[ https://issues.apache.org/jira/browse/MNG-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178369#comment-15178369
]
Christopher Tubbs commented on MNG-5987:
----------------------------------------
I don't think this issue is *just* about documenting it. The issues that were closed in favor
of this (MNG-4578, and its more informative duplicate MNG-5539) identify the fact that plugin
execution order is *NOT preserved* when the plugins are merged in from profiles. It doesn't
matter whether the current behavior is documented or not... it is still a problem that the
order is not preserved. Closing those other issues implies this is a documentation issue only...
when really it's a behavior problem.
> 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
> 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
(v6.3.4#6332)
|