- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 37 for we (0.14 sec)
-
guava-gwt/src/com/google/common/collect/Collect.gwt.xml
<module> <source path=""> <!-- Hack to keep collect from hiding collect.testing supersource: --> <exclude name="**/testing/**"/> </source> <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Mon Apr 24 14:08:06 GMT 2023 - 1.5K bytes - Viewed (0) -
build-logic-commons/code-quality-rules/src/main/resources/checkstyle/checkstyle.xml
<module name="UnusedImports"/> <module name="IllegalImport"> <!-- We shouldn't use jdk.internal types. com.beust and org.testng.collections has classes that look like Guava. We prefer to import javax.annotation and fully-qualify references to org.jetbrains.annotations. -->
XML - Registered: Wed Apr 24 11:36:11 GMT 2024 - Last Modified: Fri Dec 16 22:05:16 GMT 2022 - 6.3K bytes - Viewed (0) -
maven-core/src/test/resources/projects/past-model-version-pom.xml
KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <project> <!-- once we move past supporting modelVersion 4.0.0 we should update this version --> <modelVersion>3.9.9</modelVersion> <groupId>tests.project</groupId> <artifactId>past-model-version</artifactId> <version>1</version>
XML - Registered: Sun Mar 31 03:35:09 GMT 2024 - Last Modified: Mon Jun 03 20:33:44 GMT 2019 - 1K bytes - Viewed (0) -
guava-gwt/src/com/google/common/annotations/Annotations.gwt.xml
<module> <source path=""> <!-- Hack to keep collect from hiding collect.testing supersource: --> <exclude name="**/testing/**"/> </source> <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.3K bytes - Viewed (0) -
guava-gwt/src/com/google/common/primitives/Primitives.gwt.xml
<module> <source path=""> <!-- Hack to keep collect from hiding collect.testing supersource: --> <exclude name="**/testing/**"/> </source> <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.4K bytes - Viewed (0) -
guava-gwt/src/com/google/common/escape/Escape.gwt.xml
<module> <source path=""> <!-- Hack to keep collect from hiding collect.testing supersource: --> <exclude name="**/testing/**"/> </source> <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.4K bytes - Viewed (0) -
maven-core/src/main/resources/META-INF/maven/extension.xml
<!-- | We may potentially want to export these, but right now I'm not sure that anything Guice specific needs | to be made available to plugin authors. If we find people are getting fancy and want to take advantage of | Guice specifics we can expose that later. Really some testing needs to be done to see full hiding
XML - Registered: Sun Apr 21 03:35:09 GMT 2024 - Last Modified: Mon Jan 08 10:37:09 GMT 2024 - 12.2K bytes - Viewed (0) -
maven-compat/src/main/resources/META-INF/maven/plugin.xml
<parameter> <name>goal</name> <type>java.lang.String</type> <required>true</required> <editable>true</editable> <description>The mojo's goal that we're looking for, as an extra validation step.</description> </parameter> </parameters> <configuration> <project implementation="org.apache.maven.project.MavenProject" default-value="${project}"/>
XML - Registered: Sun Apr 21 03:35:09 GMT 2024 - Last Modified: Tue May 28 09:19:32 GMT 2013 - 9.3K bytes - Viewed (0) -
guava-gwt/pom.xml
of those modules are ones that it uses but forgets to list in its own <inherits>, we'd like to get an error. Currently we do, but if we add the extra <inherits> lines, we won't. I have one idea for a better approach, but it's painful, and I haven't tested it: We could postprocess Collect.gwt.xml to add <skip> lines for all the files that should be
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Apr 11 15:00:55 GMT 2024 - 19.8K bytes - Viewed (0) -
guava-gwt/src/com/google/common/io/Io.gwt.xml
<module> <source path=""> <!-- Hack to keep collect from hiding collect.testing supersource: --> <exclude name="**/testing/**"/> </source> <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.5K bytes - Viewed (0)