- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 33 for dies (0.14 sec)
-
maven-core/src/test/resources-project-builder/plugin-config-order/wo-plugin-mgmt/pom.xml
<version>1.0-SNAPSHOT</version> <name>Maven Integration Test :: MNG-3827</name> <description> Verify that plain plugin configuration works correctly. </description> <build> <!-- This project does not use plugin management for the test plugin --> <plugins> <plugin> <groupId>org.apache.maven.its.plugins</groupId> <artifactId>maven-it-plugin-configuration</artifactId>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 1.9K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/plugin-exec-goals-order/wo-plugin-mgmt/pom.xml
<description> Test that the goals from a plugin execution are executed in the order given by the POM, regardless whether plugin management is present or not. </description> <build> <!-- This project does not use plugin management for the test plugin --> <plugins> <plugin> <groupId>org.apache.maven.its.plugins</groupId> <artifactId>maven-it-plugin-a</artifactId> <version>1.0-SNAPSHOT</version>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 1.8K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/plugin-exec-merging/wo-plugin-mgmt/pom.xml
default id, regardless whether the id is given explicitly by the user or implicitly assumed from defaults. </description> <build> <!-- This project does not use plugin management for the test plugin --> <plugins> <plugin> <groupId>org.apache.maven.its.plugins</groupId> <artifactId>maven-it-plugin-a</artifactId> <version>2.1-SNAPSHOT</version>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 1.9K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/merged-plugin-exec-order/wo-plugin-mgmt/pom.xml
<description> Test that plugin executions (in the same phase) are properly ordered after inheritance/merge with parent executions. </description> <build> <!-- This project does not use plugin management for the test plugin --> <plugins> <plugin> <groupId>org.apache.maven.its.plugins</groupId> <artifactId>maven-it-plugin-a</artifactId> <version>1.0-SNAPSHOT</version>
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/url-no-decoding/pom.xml
<artifactId>test</artifactId> <version>1.0-SNAPSHOT</version> <packaging>jar</packaging> <name>Maven Integration Test :: MNG-4116</name> <description> Test that the project builder does not decode URLs (which must be done by the transport layer instead). </description> <!-- some URLs using percent-encoded characters --> <url>https://maven.apache.org/spacy%20path</url> <scm>
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/plugin-config-append/with-profile/subproject/pom.xml
</goals> </execution> </executions> </plugin> </plugins> </build> <profiles> <profile> <!-- an active but empty profile to ensure profile injection does not interfere with plugin configuration --> <id>child</id> <activation> <activeByDefault>true</activeByDefault> </activation> </profile> </profiles>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 2.6K bytes - Viewed (0) -
guava-gwt/pom.xml
configurations downstream, and GWT uses the runtime configuration for its builds. Thus, GWT doesn't get j2objc-annotations transitively, in contrast to the other deps of `guava`, which it does get transitively. (Arguably we should redeclare *all* the `guava` deps here.) --> <dependency> <groupId>com.google.j2objc</groupId> <artifactId>j2objc-annotations</artifactId> </dependency>
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/util/concurrent/Concurrent.gwt.xml
Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) --> <super-source path="super"/> <inherits name="com.google.common.annotations.Annotations" /> <inherits name="com.google.common.base.Base" />
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
Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) --> <super-source path="super"/> <inherits name="com.google.common.annotations.Annotations" /> <inherits name="com.google.common.base.Base" />
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
Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) --> <super-source path="super"/> <inherits name="com.google.common.annotations.Annotations" /> <inherits name="com.google.common.base.Base" />
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)