[ 
http://jira.codehaus.org/browse/MNG-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary S. Weaver updated MNG-2784:
--------------------------------

    Attachment: MNG-2784-issue-with-maven-2.0.9.tar.gz

Attaching a project that gives example of mix of different and same plugin with 
different execution ids in same phase not being executed in order that they 
appear in pom.xml (and it isn't in reverse order either).

Could this issue please be re-opened or explanation given for whether this will 
be fixed? The other bug referenced was supposedly fixed in 2.0.7, but I am 
seeing this behavior in 2.0.9.

Thanks in advance for your help!

> Multiple executions of the same plugin at the same life cycle phase in a 
> multi-module profile mixed up
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-2784
>                 URL: http://jira.codehaus.org/browse/MNG-2784
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Bootstrap & Build, Plugins and Lifecycle, Profiles, 
> Reactor and workspace
>    Affects Versions: 2.0.4, 2.0.5
>            Reporter: Maik Ebert
>            Assignee: Jason van Zyl
>            Priority: Critical
>             Fix For: 2.0.7
>
>         Attachments: MNG-2784-issue-with-maven-2.0.9.tar.gz, MNG-2784.patch
>
>
> I use the latest Maven 2.0.5 build found at 
> http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-core/2.0.5/
> I have multiple executions of the same plugin at the same life cycle phase in 
> a multi-module parent POM. There was a bug regarding the order of this 
> executions. This was fixed at 2.0.5.
> Now I needed to extract these plugin executions to a profile in this parent 
> POM. Now the executions are not ordered correctly anymore :-(
> Before (works fine):
> parent\pom.xml <= multiple executions of the same plugin at the same life 
> cycle phase in the default build element
> parent \child1\pom.xml
> parent \child2\pom.xml
> Calling mvn install in parent works fine.
> After (fails):
> parent\pom.xml <= multiple executions of the same plugin at the same life 
> cycle phase in the build element of a profile
> parent \child1\pom.xml
> parent \child2\pom.xml
> Calling mvn install in parent mixed up the execution order in the childs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to