[
https://issues.apache.org/jira/browse/MNG-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MNG-8299:
---------------------------------
Fix Version/s: 4.0.0-beta-5
> Maven 4 reverses custom lifecycle ordering
> ------------------------------------------
>
> Key: MNG-8299
> URL: https://issues.apache.org/jira/browse/MNG-8299
> Project: Maven
> Issue Type: Bug
> Components: Core
> Affects Versions: 4.0.x-candidate
> Reporter: Stefan Oehme
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: 4.0.0-beta-5
>
>
> Following this tutorial:
> [https://nextmetaphor.wordpress.com/2016/10/10/custom-maven-lifecycle/]
>
> On Maven 3.x, if you run `mvn phase3` on the project, it correctly runs phase
> 1 and 2 first and outputs
> {code:java}
> [INFO] Doing Phase 1 stuff. {code}
>
> On the 4.x nightlies, running the same command no longer runs phase 1 or 2.
> It looks like the order of phases is reversed. This happened after
> [https://github.com/apache/maven/pull/1448] was merged I think.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
