[
http://jira.codehaus.org/browse/MNG-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4919.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0.2
Assignee: Benjamin Bentmann
Fixed in [r1055486|http://svn.apache.org/viewvc?view=revision&revision=1055486]
by making implied execution ids are unique via index, {{default-goal}},
{{default-goal-1}}, etc.
> Plugin execution contributed by lifecycle mapping gets lost when same goal is
> bound multiple times
> --------------------------------------------------------------------------------------------------
>
> Key: MNG-4919
> URL: http://jira.codehaus.org/browse/MNG-4919
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle, POM
> Affects Versions: 3.0.1
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0.2
>
>
> 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|https://issues.sonatype.org/browse/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}}.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
