- Sort Score
- Result 10 results
- Languages All
Results 1 - 7 of 7 for asName (0.23 sec)
-
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) -
api/maven-api-model/src/main/mdo/maven.mdo
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Tue Apr 23 13:29:46 GMT 2024 - 115.1K bytes - Viewed (0) -
apache-maven/src/assembly/maven/conf/settings.xml
| | -s /path/to/user/settings.xml | | 2. Global Level. This settings.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}/settings.xml. | | NOTE: This location can be overridden with the CLI option: |
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/pom.xml
covered by testModule.gwt.xml. Maybe I'll try it someday. [*] https://code.google.com/p/google-web-toolkit/wiki/ResourceOracle#When_multiple_PathPrefix_es_have_the_same_path https://code.google.com/p/google-web-toolkit/issues/detail?id=7581 --> <execution> <id>gwt-test</id> <goals> <goal>test</goal>
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) -
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) -
android/pom.xml
animal-sniffer. And that would be fine for our -jre builds: If we're building with JDK8, then clearly we're sticking to JDK8 APIs. However, I assume (but did not confirm) that we'd have the same issue with our -android builds, which need animal-sniffer so that they can check that we're sticking to JDK6-like APIs.
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) -
api/maven-api-metadata/src/main/mdo/metadata.mdo
} if ( versioning.getLastUpdated() == null || versioning.getLastUpdated().length() == 0 ) { // this should only be for historical reasons - we assume local is newer versioning.setLastUpdated( v.getLastUpdated() ); } if ( v.getLastUpdated() == null || v.getLastUpdated().length() == 0
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Thu Apr 11 14:06:34 GMT 2024 - 15.8K bytes - Viewed (0)