[MNG-4332] [regression] Default plugin executions contributed by packaging execute after executions from plugin management

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0-alpha-3
• Fix Version/s: 3.0-alpha-3
• Component/s: Plugins and Lifecycle, POM
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 31/Aug/09 07:01
• Updated: 26/Feb/16 04:23
• Resolved: 31/Aug/09 16:32

Description

Given this POM snippet

<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>

the execution order with Maven 2.2.x is

1. default-resources
2. test-1
3. test-2

However, with Maven 3.x it is currently:

1. test-1
2. default-resources
3. 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.

Issue Links

• relates to: MNG-5799 Incorrect execution order of plugins in the same phase
• relates to: MNG-4345 [regression] Plugin executions contributed by default lifecycle mapping execute after other plugin executions bound to the same phase