Maven 2 & 3

Plugin execution contributed by lifecycle mapping gets lost when same goal is bound multiple times

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.0.1
  • Fix Version/s: 3.0.2
  • Component/s: Plugins and Lifecycle, POM
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

When a plugin goal is implicitly bound twice from lifecycle mappings, the two goal executions get the same id and clash. This clash can eventually lead to all but one goal execution being lost (during model merging).

Originally reported as TYCHO-546 where org.apache.maven.plugins:maven-clean-plugin:clean is bound once for the clean lifecycle (from Maven core) and once for the default lifecycle (from the build extension), both times using the execution id default-clean.

Issue Links

is related to

Improvement - An improvement or enhancement to an existing feature or task. MNG-3203 maven should execute compiler:compile and :test-compile in separate executions, to allow separate configuration

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

Activity

Hide
Permalink
Benjamin Bentmann added a comment -

Fixed in r1055486 by making implied execution ids are unique via index, default-goal, default-goal-1, etc.

Show
Benjamin Bentmann added a comment - Fixed in r1055486 by making implied execution ids are unique via index, default-goal , default-goal-1 , etc.

People

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

Dates

  • Created:
    Updated:
    Resolved: