Re: [PR] DRAFT: [MNG-5885]: prevent lifecycle phase duplication before execution [maven]

["gnodet (via GitHub)" <gi...@apache.org>]

gnodet commented on PR #13270:
URL: https://github.com/apache/maven/pull/13270#issuecomment-6040364524

   > The 'optimization' or ordering-aware mechanic is part of the discussion in slack: wether to have it or not. The Jira issue is over 8 years old, therefore I would like to understand if executing lifecycle phases from 'package compile' has any use case.
   
   I don't know any real use case for that.  If we don't consider any compatibility issue, I'd be happy with a solution that merges and reorder phases in a lifecycle.  The follow-up question however is: what happens if we have `phase1 phase2 phase3` where `phase2` belongs to a different lifecycle.  Currently, the lifecycles are not ordered in any other way than what is given on the CLI.  If we want to merge `phase1` and `phase3` in the same lifecycle execution, that means we need to choose an order, either `phase1 phase3 phase2`, or `phase2 phase1 phase3`, provided that `phase1 < phase3` in the lifecycle.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org