Hi,

regarding the last MNG-5987 comments. Could this be done for 3.4?

Regards.

Am 06/30/16 um 21:05 schrieb Christopher Tubbs (JIRA):
> 
>     [ 
> https://issues.apache.org/jira/browse/MNG-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357659#comment-15357659
>  ] 
> 
> Christopher Tubbs commented on MNG-5987:
> ----------------------------------------
> 
> It's a breaking change in behavior yes, but it's at least a predictable one. 
> I'm not sure a better way to move forward. Order of declaration is really 
> unreliable and complicated to understand when it comes to profiles and 
> parents, and I'm not sure was ever really well-defined (or at least 
> well-documented). Order of execution is also disrupted when you override an 
> execution by its execution id in a child POM, but that child's execution 
> order is different from the parent's.
> 
> Overall, I think execution id is better, and the transition cost is worth it.
> 
>> 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)
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to