[MNG-3528] Order of executing plugins in maven 2.0.9

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 2.0.9
• Component/s: Plugins and Lifecycle
• Environment: Maven 2.0.9
• Assignee: Brett Porter
• Reporter: David Bernhard
• Created: 16/Apr/08 09:42
• Updated: 12/Jun/08 21:37
• Resolved: 12/Jun/08 21:37

Description

Suppose you include a plugin like this:

<plugin>
<groupId>my.bug.test</groupId>
<artifactId>plugin</artifactId>
<version>1.0</version>
<executions>
<execution>
<id>first</id>
<phase>compile</phase>
<goals>
<goal>first</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>my.bug.test</groupId>
<artifactId>plugin</artifactId>
<version>1.0</version>
<executions>
<execution>
<id>second</id>
<phase>compile</phase>
<goals>
<goal>second</goal>
</goals>
</execution>
</executions>
</plugin>

Then SECOND will execute before FIRST. The reason is in ModelUtils.java:MergePluginDefinitions the new definition is passed as parent and the old as child - and the parent comes first in the merged executions.

However, this works correctly:

<plugin>
<groupId>my.bug.test</groupId>
<artifactId>plugin</artifactId>
<version>1.0</version>
<executions>
<execution>
<id>both</id>
<phase>test</phase>
<goals>
<goal>first</goal>
<goal>second</goal>
</goals>
</execution>
</executions>
</plugin>

I have included a tiny test case that demonstrates this. Here's my output:

[INFO] [compiler:compile]
[INFO] No sources to compile
[INFO] [:second

{execution: second}

]
SECOND
[INFO] [:first

{execution: first}

]
FIRST
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [:first

{execution: both}

]
FIRST
[INFO] [:second

{execution: both}

]
SECOND

Issue Links

• duplicates: MNG-3522 Cannot define Mojo execution order explicitly