- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 142 for We (0.15 sec)
-
maven-core/plugin-manager.txt
described the dependencies of the plugin. We are looking at using Mercury for the resolution and retrieval of the plugin dependencies so during development we would translate the POMs into dependency information that Mercury can understand, and in production we would have the pre-digested format that Mercury could utilize to resolve and retrieve dependencies. We need to be careful that we are using Mercury during development and production so that we don’t get in the situation where Maven 2.x is...
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jul 18 22:45:13 GMT 2022 - 12.9K bytes - Viewed (0) -
maven-core/src/site/apt/getting-to-container-configured-mojos.apt
--- Getting to Plexus-configured Mojos --- John Casey --- 2005-04-29 Abstract We're moving toward integrating mojos as first-class plexus components, while at the same time avoiding introducing required plexus dependencies into the mojo development model. In order to really achieve this, we need mojo configurations (which are provided both in terms of static expressions that are just looked up, and
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jan 30 15:20:35 GMT 2023 - 4.1K bytes - Viewed (0) -
maven-core/src/site/apt/configuration-management.apt
that currently we have information about a project scattered across the project.xml and the various properties files. What needs to be done is to encapsulate all of this in the POM. Typically users parameterize the use of plugins, or have custom values like ${user.name} for use in elements like the <developerConnection/>. It would be idea if we
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) -
maven-core/src/main/java/org/apache/maven/plugin/PluginParameterExpressionEvaluatorV4.java
} } /* * MNG-4312: We neither have reserved all of the above magic expressions nor is their set fixed/well-known (it * gets occasionally extended by newer Maven versions). This imposes the risk for existing plugins to * unintentionally use such a magic expression for an ordinary property. So here we check whether we
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Jan 30 23:39:19 GMT 2024 - 9.8K bytes - Viewed (0) -
maven-core/src/test/java/org/apache/maven/lifecycle/LifecycleExecutorTest.java
@Test void testCalculationOfBuildPlanWithIndividualTaskWherePluginIsSpecifiedInThePom() throws Exception { // We are doing something like "mvn resources:resources" where no version is specified but this // project we are working on has the version specified in the POM so the version should come from there. File pom = getProject("project-basic");
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Jan 09 20:57:17 GMT 2024 - 24.7K bytes - Viewed (0) -
maven-compat/src/test/java/org/apache/maven/artifact/transform/TransformationManagerTest.java
"We expected the release transformation and got " + tms.get(0)); assertTrue( tms.get(1) instanceof LatestArtifactTransformation, "We expected the latest transformation and got " + tms.get(1)); assertTrue( tms.get(2) instanceof SnapshotTransformation, "We expected the snapshot transformation and got " + tms.get(2));
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Thu Apr 25 05:46:50 GMT 2024 - 2.3K bytes - Viewed (0) -
maven-compat/src/test/java/org/apache/maven/project/inheritance/t02/ProjectInheritanceTest.java
* the final model of the project being assembled. There is no * overriding going on amongst the models being used in this test: * each model in the lineage is providing a value that is not present * anywhere else in the lineage. We are just making sure that values * down in the lineage are bubbling up where they should. * */ @Deprecated class ProjectInheritanceTest extends AbstractProjectInheritanceTestCase {
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Thu Apr 25 05:46:50 GMT 2024 - 6.2K bytes - Viewed (0) -
maven-core/src/main/resources/META-INF/maven/extension.xml
<!-- | 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) -
maven-core/src/main/java/org/apache/maven/internal/impl/Graph.java
} cycle.removeLast(); stateMap.put(v, DfsState.VISITED); } else if (state == DfsState.VISITING) { // we are already visiting this vertex, this mean we have a cycle int pos = cycle.lastIndexOf(v.label); List<String> ret = cycle.subList(pos, cycle.size()); ret.add(v.label); return ret;
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 4.5K bytes - Viewed (0) -
maven-api-impl/src/main/java/org/apache/maven/internal/impl/model/DefaultModelProcessor.java
* * As a non-default component this now gets a negative priority relative to other implementations * of the same interface. Since we want to allow overriding this doesn't matter in this case. * (if it did we could add @Priority of 0 to match the priority given to default components.) */ @Named @Singleton public class DefaultModelProcessor implements ModelProcessor {
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 5.8K bytes - Viewed (0)