- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 15 for v3phases (0.08 sec)
-
impl/maven-core/src/main/java/org/apache/maven/internal/impl/DefaultLifecycleRegistry.java
@Override public List<Plugin> plugins() { Map<String, LifecyclePhase> lfPhases = lifecycle.getDefaultLifecyclePhases(); LifecyclePhase phase = lfPhases != null ? lfPhases.get(name) : null; if (phase != null) { Map<String, Plugin> plugins = new LinkedHashMap<>();Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Mon Sep 29 14:45:25 UTC 2025 - 20.1K bytes - Viewed (0) -
impl/maven-core/src/main/java/org/apache/maven/lifecycle/internal/DefaultLifecycleExecutionPlanCalculator.java
Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Tue Mar 25 09:45:07 UTC 2025 - 26.7K bytes - Viewed (0) -
impl/maven-core/src/main/java/org/apache/maven/ReactorReader.java
String phase = event.getMojoExecution().getLifecyclePhase(); if (phase != null) { Deque<String> phases = getLifecycles(project); if (!Objects.equals(phase, phases.peekLast())) { phases.addLast(phase); if ("clean".equals(phase)) { synchronized (project) {
Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Mon Dec 15 11:20:38 UTC 2025 - 24.4K bytes - Viewed (0) -
docs/SMB3_IMPLEMENTATION_PLAN.md
- 1 QA engineer for test infrastructure - 1 DevOps engineer for CI/CD setup ### Timeline - **Total Duration**: 6-8 months for all features - **Phases 1-2**: 2-3 months (High priority) - **Phases 3-4**: 2 months (Medium priority) - **Phases 5-6**: 2-3 months (Low priority) ### Infrastructure - Windows Server test lab - RDMA-capable test hardware - Continuous integration environment
Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sat Aug 16 02:53:50 UTC 2025 - 10.7K bytes - Viewed (0) -
impl/maven-cli/src/main/java/org/apache/maven/cling/invoker/mvnsh/builtin/BuiltinShellCommandRegistryFactory.java
Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Sat Jun 07 06:22:47 UTC 2025 - 12.3K bytes - Viewed (0) -
impl/maven-cli/src/main/java/org/apache/maven/cling/invoker/mvnup/goals/ModelUpgradeStrategy.java
} } /** * Upgrades deprecated Maven 3 phase names to Maven 4 equivalents. * This replaces pre-/post- phases with before:/after: phases. */ private void upgradeDeprecatedPhases(Editor editor, UpgradeContext context) { // Create mapping of deprecated phases to their Maven 4 equivalents Map<String, String> phaseUpgrades = createPhaseUpgradeMap(); Element root = editor.root();Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Tue Nov 18 18:03:26 UTC 2025 - 16.6K bytes - Viewed (0) -
impl/maven-cli/src/test/java/org/apache/maven/cling/invoker/mvnup/goals/ModelUpgradeStrategyTest.java
assertTrue(result.success(), "Model upgrade should succeed"); assertTrue(result.modifiedCount() > 0, "Should have upgraded phases"); // Verify phases were upgraded verifyCleanPluginPhases(document); verifyFailsafePluginPhases(document); verifySitePluginPhases(document);Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Tue Nov 18 18:03:26 UTC 2025 - 38.8K bytes - Viewed (0) -
api/maven-api-core/src/main/java/org/apache/maven/api/services/ProjectManager.java
* Attached artifacts are secondary artifacts produced during the build (e.g., sources jar, * javadoc jar, test jars). These artifacts are created and attached during specific * lifecycle phases, so the collection contents depend on the build phase when this method * is called. * * @param project the project to get attached artifacts for
Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Thu Jan 30 23:29:13 UTC 2025 - 12K bytes - Viewed (0) -
impl/maven-core/plugin-manager.txt
These particular phases in a plugin’s lifecycle can probably be generalized to all plugins so could be something implemented in all plugins. Here we could have the descriptor either point to methods for each of these phases to execute or we could create a lifecycle in Plexus for these phases. For a particular application plugin there will be a declarative descriptor for that plugin type.
Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Wed Jan 22 11:03:29 UTC 2025 - 12.3K bytes - Viewed (0) -
api/maven-api-plugin/src/main/mdo/plugin.mdo
associated with a Maven project can lack a file. As such, this annotation is meant for Mojos that only want to analyze the set of transitive dependencies, in particular during early lifecycle phases where full dependency resolution might fail due to projects which haven't been built yet. </description> </field> <field> <name>dependencyCollection</name>Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Tue Feb 25 08:28:41 UTC 2025 - 24.8K bytes - Viewed (0)