[MNG-3887] [regression] Order of plugin executions within same phase does not match POM order when plugin management is used

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0-alpha-1
• Fix Version/s: 3.0-alpha-2
• Component/s: Plugins and Lifecycle
• Assignee: Britton Isbell
• Reporter: Benjamin Bentmann
• Created: 02/Dec/08 11:51
• Updated: 25/Jan/09 21:24
• Resolved: 25/Jan/09 21:24

Description

For a POM snippet like

<executions>
  <execution>
    <id>test-1</id>
    <phase>validate</phase>
    <goals>
      <goal>one</goal>
    </goals>
  </execution>
  <execution>
    <id>test-2</id>
    <phase>validate</phase>
    <goals>
      <goal>two</goal>
    </goals>
  </execution>
</executions>

the effective goal execution order is either [one, two] or [two, one] depending on the usage of <pluginManagement> for the plugin in question.

Issue Links

• is related to: MNG-3886 [regression] Ordering of goals from a plugin execution is not respected if plugin management applies
• relates to: MNG-3925 [regression] Wrong order of plugin executions after merge with executions inherted from parent