[MNG-4345] [regression] Plugin executions contributed by default lifecycle mapping execute after other plugin executions bound to the same phase

• 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
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 08/Sep/09 04:14
• Updated: 03/Jun/23 07:14
• Resolved: 08/Sep/09 07:24

Description

For the following snippet

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

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.

Issue Links

• is related to: MNG-4332 [regression] Default plugin executions contributed by packaging execute after executions from plugin management
• is related to: MNG-4341 [regression] Plugins are not executed in POM order
• relates to: MNG-5799 Incorrect execution order of plugins in the same phase
• relates to: MNG-5987 Document the algorithm calculating the order of plugin executions inside a phase.
• mentioned in: Page Loading...