- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for Wade (0.12 sec)
-
api/maven-api-model/src/main/mdo/maven.mdo
<field> <name>pluginManagement</name> <version>4.0.0+</version> <required>false</required> <description>Default plugin information to be made available for reference by projects derived from this one. This plugin configuration will not be resolved or bound to the lifecycle unless referenced. Any local configuration for a given plugin will override
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) -
maven-core/src/main/resources/META-INF/maven/extension.xml
<exportedPackage>jakarta.annotation.*</exportedPackage> <!-- | We may potentially want to export these, but right now I'm not sure that anything Guice specific needs | to be made available to plugin authors. If we find people are getting fancy and want to take advantage of | Guice specifics we can expose that later. Really some testing needs to be done to see full hiding
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jan 08 10:37:09 GMT 2024 - 12.2K bytes - Viewed (0) -
api/maven-api-toolchain/src/main/mdo/toolchains.mdo
and match them against the toolchain requirements of the project (as configured in {@code pom.xml}): 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
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)