- Sort Score
- Result 10 results
- Languages All
Results 21 - 30 of 35 for isSame (0.21 sec)
-
maven-core/src/test/resources-project-builder/merged-plugin-exec-order/wo-plugin-mgmt/sub/pom.xml
<artifactId>parent</artifactId> <version>0.1</version> </parent> <artifactId>child</artifactId> <name>Maven Integration Test :: MNG-3925</name> <description> Test that plugin executions (in the same phase) are properly ordered after inheritance/merge with parent executions. </description> <build> <plugins> <plugin> <groupId>org.apache.maven.its.plugins</groupId>
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-deps/pom.xml
<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> <version>1.0-SNAPSHOT</version> <dependencies> <!-- NOTE: That's exactly the same dependency as for the other plugin. -->
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) -
guava-gwt/src/com/google/common/util/concurrent/Concurrent.gwt.xml
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 Java package; see https://goo.gl/pRV3Yn for details. The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Tue Jul 19 04:29:50 GMT 2022 - 1.5K bytes - Viewed (0) -
guava-gwt/src/com/google/common/cache/Cache.gwt.xml
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 Java package; see https://goo.gl/pRV3Yn for details. The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.6K bytes - Viewed (0) -
guava-gwt/test/com/google/common/collect/testing/google/Google.gwt.xml
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 Java package; see https://goo.gl/pRV3Yn for details. The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.7K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/plugin-exec-order/wo-plugin-mgmt/pom.xml
<artifactId>test</artifactId> <version>0.1</version> <packaging>pom</packaging> <name>Maven Integration Test :: MNG-3887</name> <description> Test that multiple plugin executions bound to the same phase are executed in the order given by the POM. </description> <build> <!-- This project does not use plugin management for the test plugin --> <plugins> <plugin>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 2K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/repo-inheritance/pom.xml
<artifactId>maven-it-it0043</artifactId> <version>1.0-SNAPSHOT</version> <name>Maven Integration Test :: it0043</name> <description>Test for repository inheritance - ensure using the same id overrides the defaults</description> <repositories> <repository> <id>central</id> <name>it0043</name> <url>file:///${basedir}/target/maven-core-it0043-repo</url> </repository>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 2K bytes - Viewed (0) -
apache-maven/src/assembly/maven/conf/toolchains.xml
| | -t /path/to/user/toolchains.xml | | 2. Global Level. This toolchains.xml file provides configuration for all Maven | users on a machine (assuming they're all using the same Maven | installation). It's normally provided in | ${maven.conf}/toolchains.xml. | | NOTE: This location can be overridden with the CLI option: |
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Thu Dec 24 18:09:10 GMT 2020 - 3.5K bytes - Viewed (0) -
api/maven-api-toolchain/src/main/mdo/toolchains.mdo
if match is found, the toolchain instance is made available to other Maven plugins.</p> <p>With {@code jdk} toolchain, for example, instead of being stuck with the JDK used to run Maven, all plugins can use the same other JDK instance without hardcoding absolute paths into the {@code pom.xml} and without configuring every plugin that require path to JDK tools.</p>
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Wed Feb 07 21:28:01 GMT 2024 - 8.5K bytes - Viewed (0) -
guava-gwt/src/com/google/thirdparty/publicsuffix/PublicSuffixType.gwt.xml
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 Java package; see https://goo.gl/pRV3Yn for details. The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one
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)