[jira] (MNG-2258) Wrong execution order of plugins in same phase

["Karsten Gresch (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=334401#comment-334401 ] 

Karsten Gresch commented on MNG-2258:
-------------------------------------

As per my tests, this unpleasant bug still exists for 3.04 and 3.05. Tested with maven-jar-plugin, maven-assembly-plugin and copy-maven-plugin, all executed in phase 'package'.

Perhaps it's a bug in the latter plugin though it seems to me that it is very well crafted (despite the artifact naming perhaps).

I just don't have the time getting into Maven internal's to change the execution mechanism, but as per my opinion, Maven should control the execution order and no plugin should be able to break out from Maven's control.

Anyway - very, very unpleasant. The only workaround I see when not creating pseudo-projects for dependent packaging executions is creating multiple profiles and calling them in the correct order.

Could somebody please open this ticket again? From my point of view, specifying the execution order is quite important in the packaging phase and if Maven's goal is supporting the entire development lifecycle, it *must* support this.

Cheers,

Karsten

Twitter: @gresch
                
> Wrong execution order of plugins in same phase
> ----------------------------------------------
>
>                 Key: MNG-2258
>                 URL: https://jira.codehaus.org/browse/MNG-2258
>             Project: Maven 2 & 3
>          Issue Type: Bug
>    Affects Versions: 2.0.4
>         Environment: N/A
>            Reporter: David J. M. Karlsen
>            Assignee: Benson Margulies
>            Priority: Blocker
>             Fix For: 3.0.3
>
>         Attachments: mavenTest.zip
>
>
> AFAIK plugins should be execute in the same order as they are listed in the POM, when bound to the same phase. This does not happen, the execution order is arbitrary.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira