- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 34 for save (9.15 sec)
-
guava-gwt/src/com/google/common/collect/Collect.gwt.xml
tests, either. This causes it to fail to find AtomicLongMapTest. 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"/>
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) -
api/maven-api-plugin/src/main/mdo/plugin.mdo
Flags this Mojo as requiring information about the dependencies that would make up the specified class path. As the name suggests, this is similar to requiresDependencyResolution and supports the same values. The important difference is this will not resolve the files for the dependencies, i.e. the artifacts associated with a Maven project can lack a file. As such, this annotation is meant for Mojos that only
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sun Apr 14 17:14:22 GMT 2024 - 23.6K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/unique-repo-id/artifact-repo/pom.xml
<artifactId>test</artifactId> <version>0.1</version> <packaging>jar</packaging> <name>Maven Integration Test :: MNG-4193</name> <description> Test that multiple artifact repository declarations with the same id cause a validation error. </description> <repositories> <repository> <id>one</id> <url>https://repo1.maven.org/maven2</url> </repository> <repository> <id>one</id>
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/plugin-exec-merging/wo-plugin-mgmt/sub/pom.xml
<version>0.1</version> </parent> <artifactId>child</artifactId> <name>Maven Integration Test :: MNG-3938</name> <description> Test that plugin executions with the same id are merged during inheritance, especially executions using the default id, regardless whether the id is given explicitly by the user or implicitly assumed from defaults. </description> <build> <plugins>
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-order-with-lifecycle/pom.xml
<packaging>JAR</packaging> <name>Maven Integration Test :: MNG-4341</name> <description> Test that plugins bound to the same phase get executed in POM order even if one of the plugins participates in the default lifecycle bindings for the project's packaging. </description> <build> <plugins> <plugin>
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-compat/src/main/resources/META-INF/maven/plugin.xml
<type>org.apache.maven.project.MavenProject</type> <required>true</required> <editable>false</editable> <description>The current MavenProject instance, which will have a new executionProject set after execution.</description> </parameter> <parameter> <name>session</name> <type>org.apache.maven.execution.MavenSession</type>
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Tue May 28 09:19:32 GMT 2013 - 9.3K bytes - Viewed (0) -
apache-maven/src/assembly/maven/conf/settings.xml
| | It works like this: a POM may declare a repository to use in resolving certain artifacts. | However, this repository may have problems with heavy traffic at times, so people have mirrored | it to several places. | | That repository definition will have a unique id, so we can create a mirror reference for that | repository, to be used as an alternate download site. The mirror site will be the preferred
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Jun 19 15:06:01 GMT 2023 - 11K bytes - Viewed (0) -
guava-gwt/src/com/google/common/io/Io.gwt.xml
tests, either. This causes it to fail to find AtomicLongMapTest. 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"/>
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) -
guava-gwt/src/com/google/common/math/Math.gwt.xml
tests, either. This causes it to fail to find AtomicLongMapTest. 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"/>
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) -
guava-gwt/src/com/google/thirdparty/publicsuffix/PublicSuffixPatterns.gwt.xml
tests, either. This causes it to fail to find AtomicLongMapTest. 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"/>
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)