Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
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 :
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
-
MNG-3203
maven should execute compiler:compile and :test-compile in separate executions, to allow separate configuration
-
Activity
Benjamin Bentmann
made changes -
Benjamin Bentmann
made changes -
| Status | Open [ 1 ] | Closed [ 6 ] |
| Assignee | Benjamin Bentmann [ bentmann ] | |
| Fix Version/s | 3.0.2 [ 16952 ] | |
| Resolution | Fixed [ 1 ] |
Fixed in r1055486 by making implied execution ids are unique via index, default-goal, default-goal-1, etc.