- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for Doesn (0.28 sec)
-
guava-gwt/pom.xml
packages, like RangeTest. The reason for this is that GWT doesn't distinguish between .java files in c.g.c.collect.Collect, a module that the c.g.c.base test module inherits, and .java files in c.g.c.collect.testModule, one that it doesn't[*]. Consequently, c.g.c.base.testModule transitively pulls in .java files from both modules while reading
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) -
maven-core/src/test/resources-project-builder/id-container-joining-with-empty-elements/pom.xml
<version>0.1</version> <packaging>pom</packaging> <name>Maven Integration Test :: MNG-3979</name> <description> Test that during inheritance the merging/joining of subtrees with equal identifier doesn't crash if the parent POM has a non-empty element and the child POM has an empty element to join. </description> <properties> <prop0>test</prop0> </properties> <repositories> <repository>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jul 18 17:22:19 GMT 2022 - 2.8K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/plugin-management-inheritance/pom.xml
<artifactId>maven-it-it0052</artifactId> <version>1.0</version> <packaging>jar</packaging> <name>Maven Integration Test :: it0052</name> <description>Test that source attachment doesn't take place when -DperformRelease=true is missing.</description> <!-- NOTE: Use stub versions of the core plugins referenced by the build --> <build> <pluginManagement> <plugins> <plugin>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 2.1K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/equal-plugin-exec-ids/pom.xml
<artifactId>test</artifactId> <version>1.0-SNAPSHOT</version> <name>Maven Integration Test :: MNG-3821</name> <description> Verify that using the same id for executions/reportsets of different plugins doesn't blow up the project builder. </description> <build> <plugins> <plugin> <groupId>org.apache.maven.its.plugins</groupId> <artifactId>maven-it-plugin-a</artifactId>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 2.5K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/id-container-joining-with-empty-elements/sub/pom.xml
</parent> <artifactId>child</artifactId> <name>Maven Integration Test :: MNG-3979</name> <description> Test that during inheritance the merging/joining of subtrees with equal identifier doesn't crash if the parent POM has a non-empty element and the child POM has an empty element to join. </description> <properties/> <repositories> <repository> <id>equal-repo-id</id>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jul 18 17:22:19 GMT 2022 - 2.3K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/xml-markup-interpolation/pom.xml
<version>0.1-SNAPSHOT</version> <packaging>jar</packaging> <name>Maven Integration Test :: MNG-3924</name> <description> Test that interpolation of properties that resolve to XML markup doesn't crash the project builder. </description> <properties> <!-- That's the property containing escaped XML markup --> <xmlMarkup><?xml version='1.0'?>Tom&Jerry</xmlMarkup>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 1.4K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/equal-plugin-deps/pom.xml
<artifactId>test</artifactId> <version>1.0-SNAPSHOT</version> <name>Maven Integration Test :: MNG-3838</name> <description> Verify that using the same dependency for different plugins doesn't blow up the project builder. </description> <build> <plugins> <plugin> <groupId>org.apache.maven.its.plugins</groupId> <artifactId>maven-it-plugin-a</artifactId>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 2.3K bytes - Viewed (0) -
android/pom.xml
obvious way to ensure that. We could consider arranging things so that only the tests we know need this would get the add-opens. Right now that doesn't seem worth the effort, though. --> <test.add.opens> --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Tue Mar 12 20:26:18 GMT 2024 - 19.4K bytes - Viewed (0)