[regression] Default plugin executions contributed by packaging execute after
executions from plugin management
---------------------------------------------------------------------------------------------------------------
Key: MNG-4332
URL: http://jira.codehaus.org/browse/MNG-4332
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle, POM
Affects Versions: 3.0-alpha-3
Reporter: Benjamin Bentmann
Given this POM snippet
{code:xml}
<build>
<pluginManagement>
<plugins>
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<version>2.2</version>
<executions>
<execution>
<id>test-1</id>
<goals>
<goal>resources</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</pluginManagement>
<plugins>
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<version>2.2</version>
<executions>
<execution>
<id>test-2</id>
<goals>
<goal>resources</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
{code}
the execution order with Maven 2.2.x is
# default-resources
# test-1
# test-2
However, with Maven 3.x it is currently:
# test-1
# default-resources
# test-2
This causes a compilation failure on {{maven-core}} from the 2.2.x branch when
build with 3.x because the compiler executions happen in the wrong order.
--
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
