- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for tight (0.15 sec)
-
maven-core/src/main/java/org/apache/maven/lifecycle/DefaultLifecycles.java
if (lookup == null) { return customLifecycles != null ? customLifecycles : new HashMap<>(); } // Lifecycles cannot be cached as extensions might add custom lifecycles later in the execution. try { Map<String, Lifecycle> lifecycles = new HashMap<>(lookup.lookupMap(Lifecycle.class)); for (org.apache.maven.api.Lifecycle lf : registry) {
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 6K bytes - Viewed (0) -
maven-bom/src/site/site.xml
<options> <disableCookies/> <trackPageView/> <enableLinkTracking/> </options> </matomo> </custom> <publishDate position="right" /> <version position="right" /> <body> <breadcrumbs> <item name="Apache" href="https://www.apache.org/" /> <item name="Maven" href="https://maven.apache.org/index.html" /> <item name="Ref" href="../" />
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sun Mar 24 21:16:47 GMT 2024 - 2.4K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/resolver/MavenChainedWorkspaceReader.java
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 5.6K bytes - Viewed (0) -
maven-core/src/site/apt/configuration-management.apt
${maven.home} | +--- maven.properties +-----+ * Group configuration As far as properties go for an entire build the maven.properties could be placed at the top of the group but I'm not really sure how this might work. There could probably also be a directory for plugins.xml and maven.properties. * Project configuration At the project level all configuration is achieved by tweaking the POM. One of the differences between
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Mar 18 00:24:53 GMT 2024 - 5.8K bytes - Viewed (0)