[MNG-3522] Cannot define Mojo execution order explicitly

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.0.9
• Component/s: FDPFC, Plugins and Lifecycle
• Assignee: Unassigned
• Reporter: Thomas Diesler
• Created: 14/Apr/08 08:16
• Updated: 05/Jun/23 06:40
• Resolved: 05/Jun/23 06:40

Description

In this example antrun:run is excuted after dependency:copy-dependencies by virtue of plugin order. Preferable would be an explicit order definition. For example, a plugin could export a 'phase-id' that another uses in its 'phase' element.

<plugins>
  <plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-dependency-plugin</artifactId>
    <executions>
      <execution>
        <id>copy-dependencies</id>
        <phase>package</phase>
        <goals>
          <goal>copy-dependencies</goal>
        </goals>
        <configuration>
          <outputDirectory>${project.build.directory}/thirdparty</outputDirectory>
          <stripVersion>true</stripVersion>
        </configuration>
      </execution>
    </executions>
  </plugin>
  <plugin>
    <artifactId>maven-antrun-plugin</artifactId>
    <executions>
      <execution>
        <phase>package</phase>
        <goals>
          <goal>run</goal>
        </goals>
        <configuration>
          <tasks>
            <ant antfile="ant/build-concat.xml"/>
          </tasks>
        </configuration>
      </execution>
    </executions>
  </plugin>
</plugins>

Issue Links

• is duplicated by: MNG-3528 Order of executing plugins in maven 2.0.9
• is duplicated by: MNG-5994 add explicit ordering support for plugins
• is duplicated by: MNG-4727 Allow ordering plugin execution via <id/>
• is duplicated by: MNG-5090 Maven End Users should be able to control the execution order of plugins without creating a custom Lifecycle and Package Type
• is related to: MNG-5987 Document the algorithm calculating the order of plugin executions inside a phase.
• mentioned in: Page Loading...