You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Maik Ebert (JIRA)" <ji...@codehaus.org> on 2007/01/18 15:00:09 UTC

[jira] Commented: (MNG-2784) Multiple executions of the same plugin at the same life cycle phase in a multi-module profile mixed up

    [ http://jira.codehaus.org/browse/MNG-2784?page=comments#action_85357 ] 
            
Maik Ebert commented on MNG-2784:
---------------------------------

Maybe MNG-2784 does not fix this special configuration.

> 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: Plugins and Lifecycle, Bootstrap & Build, Reactor and workspace, Profiles
>    Affects Versions: 2.0.5, 2.0.4
>            Reporter: Maik Ebert
>            Priority: Critical
>
> 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