[regression] Plugin executions contributed by default lifecycle mapping execute
after other plugin executions bound to the same phase
-------------------------------------------------------------------------------------------------------------------------------------
Key: MNG-4345
URL: http://jira.codehaus.org/browse/MNG-4345
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 3.0-alpha-3
Reporter: Benjamin Bentmann
For the following snippet
{code:xml}
<plugin>
<groupId>org.apache.maven.its.plugins</groupId>
<artifactId>maven-it-plugin-log-file</artifactId>
<version>2.1-SNAPSHOT</version>
<executions>
<execution>
<phase>process-resources</phase>
<goals>
<goal>log-string</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
<version>0.1-stub-SNAPSHOT</version>
</plugin>
{code}
where both maven-it-plugin-log-file and maven-resources-plugin bind executions
to the lifecycle phase "process-resources" and maven-resources-plugin is
declared after maven-it-plugin-log-file with respect to POM order, trunk
executes the goal {{log-string}} before {{resources}}, in contrast to Maven 2.
--
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
