Hey, First of all: Thanks for the feedback! I will follow the least invasive idea since I got the feedback that...: * we have use cases that make use of (seemingly) duplicated lifecycle executions in a certain order. (thanks Jon!) * we don't know, if there is any (common) use case I might break with Option 3 or 4. but a log message might wake people that are not aware of this. (thanks Matthias) * https://github.com/apache/maven/pull/13532 already provides a solution for Maven 4, see also the comment https://github.com/apache/maven/pull/13270#issuecomment-6203265187 on my pr. (thanks Guillaume) -> Option 2 has won: Provide a warn message and don't change the current (legacy) behaviour. Thanks, Sebastian
> Sebastian Tiemann <[email protected]> hat am 02.10.2026 10:58 MESZ > geschrieben: > > > hey all, > > I had a look at this oldie https://issues.apache.org/jira/browse/MNG-5885 and > that made me think about how to better handle maven executions like 'mvn > package compile'. > > I would love to hear you thoughts about it. Here are some ideas: > * Execute everything with all duplicate lifecycle phases and to nothing > (current state) > * Execute everything with all duplicate lifecycle phases and print a log > message, e.g. warn > * Filter the duplicate lifecycle phases and only execute the lifecycle phases > from install in this case. Print a log message, e.g. warn > o the filtering code could look like this: > https://github.com/apache/maven/pull/13270 > o hint: this also includes removing lifecycles from duplicated goals in a > specific order > * Throw an error: Doing this is a bad idea. > > Thanks, > Sebastian >
