- Sort Score
- Result 10 results
- Languages All
Results 1 - 7 of 7 for mucho (0.23 sec)
-
maven-core/src/test/java/org/apache/maven/lifecycle/MavenExecutionPlanTest.java
MavenExecutionPlan plan = LifecycleExecutionPlanCalculatorStub.getProjectAExecutionPlan(); assertNull(plan.findLastInPhase("pacXkage")); // Beer comes straight after package in stub, much like real life. assertNotNull(plan.findLastInPhase(LifecycleExecutionPlanCalculatorStub.INITIALIZE.getPhase())); }
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Wed Sep 06 08:39:32 GMT 2023 - 2.8K bytes - Viewed (0) -
maven-core/src/test/java/org/apache/maven/lifecycle/internal/stub/AboutTheStubs.html
used to test the individual components in the lifecycle with data that has expected characteristics and can be asserted as desired. You can change/extend these stubs, and tests should not be breaking too much, since most tests assert using expected values from the stubs. Normally, when you try to use data from the stubs that have not been properly populated, you'll get a nullpointer in your test and you then have to
HTML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Jul 02 16:47:10 GMT 2021 - 2.3K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/lifecycle/internal/ProjectSegment.java
* lifecycle at all, in which case we wouldn't be needing this class at all ( and * ProjectBuildList.getByTaskSegments). Or maybe they should be introduced in the calculation * of the execution plan instead, which seems much nicer. * </p> * <p> * Additionally this class contains a clone of the MavenSession, which is *only* needed * because it has as notion of a "current" project. * </p>
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Wed Sep 06 08:39:32 GMT 2023 - 3.5K bytes - Viewed (0) -
maven-core/src/site/apt/offline-mode.apt
All of these operations will produce their own unique errors in the absence of a coordinated offline strategy. In addition, efforts to unite these failing behaviors behind a consistent user interface is much, much more difficult if the system can't tell whether it has access to the network required by these operations. Offline mode really means anticipating a lack of network connectivity, and as
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Mar 18 00:24:53 GMT 2024 - 10.6K bytes - Viewed (0) -
maven-compat/src/main/resources/META-INF/maven/plugin-expressions/project.paramdoc.xml
</dependencies> ]]></configuration> <description> <![CDATA[ This is a set of Artifact instances resolved from the set of dependencies for the current project. NOTE: This will likely contain much more than the direct dependencies of the current POM, since Maven uses transitive, or chained, dependency resolution. ]]></description> </expression> <expression> <syntax>project.parentArtifact</syntax>
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sun Nov 23 12:04:30 GMT 2014 - 5.6K bytes - Viewed (0) -
maven-compat/src/main/java/org/apache/maven/artifact/repository/metadata/DefaultRepositoryMetadataManager.java
// snapshot timestamp, or some other timestamp later encoded into the metadata. // TODO this needs to be repeated here so the merging doesn't interfere with the written metadata // - we'd be much better having a pristine input, and an ongoing metadata for merging instead Map<ArtifactRepository, Metadata> previousMetadata = new HashMap<>(); ArtifactRepository selected = null;
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 18.9K bytes - Viewed (0) -
maven-core/plugin-manager.txt
h3. Plugins need a specific metadata model Each application will have its own model for plugins. Much of this model will be common across applications but there will always be issues specific to a particular applications’s plugins. Some of the issues that need to be taken into consideration: * Plugin dependencies
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Jul 18 22:45:13 GMT 2022 - 12.9K bytes - Viewed (0)