[regression] Plugins are not properly ordered after merging with profile plugins
--------------------------------------------------------------------------------
Key: MNG-4416
URL: http://jira.codehaus.org/browse/MNG-4416
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle, POM, Profiles
Affects Versions: 3.0-alpha-3
Reporter: Benjamin Bentmann
Basically the same as MNG-4415 just in the context of profiles. E.g. for a POM
with
{code:xml}
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.its.plugins</groupId>
<artifactId>maven-it-plugin-b</artifactId>
<version>2.1-SNAPSHOT</version>
</plugin>
</plugins>
</build>
<profiles>
<profile>
<id>test</id>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.its.plugins</groupId>
<artifactId>maven-it-plugin-a</artifactId>
<version>2.1-SNAPSHOT</version>
</plugin>
<plugin>
<groupId>org.apache.maven.its.plugins</groupId>
<artifactId>maven-it-plugin-b</artifactId>
<version>2.1-SNAPSHOT</version>
</plugin>
</plugins>
</build>
</profile>
</profiles>
{code}
the effective model erroneously ends up with the wrong plugin order as shown
below when the profile is activated:
{code:xml}
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.its.plugins</groupId>
<artifactId>maven-it-plugin-b</artifactId>
<version>2.1-SNAPSHOT</version>
</plugin>
<plugin>
<groupId>org.apache.maven.its.plugins</groupId>
<artifactId>maven-it-plugin-a</artifactId>
<version>2.1-SNAPSHOT</version>
</plugin>
</plugins>
</build>
{code}
In general, profile injection is expected to work like this when merging the
plugin lists:
{noformat}
model: X -> A -> B -> D -> E
profile: Y -> A -> C -> D -> F
result: X -> Y -> A -> B -> C -> D -> E -> F
{noformat}
--
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
