Maven 2 & 3

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

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.0-alpha-3
  • Fix Version/s: 3.0-alpha-3
  • Component/s: Plugins and Lifecycle
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

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

Bug - A problem which impairs or prevents the functions of the product. MNG-4332 [regression] Default plugin executions contributed by packaging execute after executions from plugin management

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MNG-4341 [regression] Plugins are not executed in POM order

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Benjamin Bentmann added a comment -

This was caused by my changes for MNG-4341. In trying to express all the plugin executions solely by means of the POM, it got apparent that the POM is not capable to describe the executional model of Maven 2.x. Plugin executions contributed by default lifecycle mappings are treated differently than ordinary plugin executions but the POM doesn't provide the means to tell those two kinds of plugin executions apart.

Show
Benjamin Bentmann added a comment - This was caused by my changes for MNG-4341 . In trying to express all the plugin executions solely by means of the POM, it got apparent that the POM is not capable to describe the executional model of Maven 2.x. Plugin executions contributed by default lifecycle mappings are treated differently than ordinary plugin executions but the POM doesn't provide the means to tell those two kinds of plugin executions apart.
Hide
Permalink
Benjamin Bentmann added a comment -

Fixed in r812467.

Show
Benjamin Bentmann added a comment - Fixed in r812467 .
Hide
Permalink
Benjamin Bentmann added a comment -

Revised initial fix in r812480.

Show
Benjamin Bentmann added a comment - Revised initial fix in r812480 .

People

  • Assignee:
    Benjamin Bentmann
    Reporter:
    Benjamin Bentmann
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: