[
https://issues.apache.org/jira/browse/MNG-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228449#comment-17228449
]
Delany commented on MNG-5987:
-----------------------------
I don't want to have to rename default plugin executions in order to line them
all up correctly.
Rather introduce an execution *priority* tag, with possible values 0-255. That
way you don't break existing functionality. You could also make a
maven-enforcer-plugin rule that finds clashing priority values.
> Document the algorithm calculating the order of plugin executions.
> ------------------------------------------------------------------
>
> Key: MNG-5987
> URL: https://issues.apache.org/jira/browse/MNG-5987
> Project: Maven
> Issue Type: Improvement
> Components: Documentation: General
> Reporter: Christian Schulte
> Priority: Critical
>
> Users continuously report issues regarding the order of plugin executions:
> repeating that this order is not expected to be guaranteed inside a phase is
> not convincing for them.
> The algorithm used to calculate the order of executions performed by Maven
> needs to be documented:
> - declaration order in the POM
> - inheritance merging from parent POM,
> - merging of profiles and other plugin containers,
> - the order of executions of multiple executions in the same lifecycle phase,
> etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
