[
https://jira.codehaus.org/browse/MNG-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312180#comment-312180
]
Anders Hammar commented on MNG-5359:
------------------------------------
Some investigation shows that this seems specific to the clean plugin (doesn't
happen for the enforcer plugin for example). I'm guessing this is because the
clean plugin has bindings to the clean lifecycle.
> Declared execution in PluginMgmt gets bound to lifecycle (regression)
> ---------------------------------------------------------------------
>
> Key: MNG-5359
> URL: https://jira.codehaus.org/browse/MNG-5359
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 3.0.1, 3.0.2, 3.0.3, 3.0.4
> Environment: Mac OS 10.7.5, Apple JDK 1.6.0_35
> (Same behavior seen on Windows XP with Sun JDK 1.6.0 as well)
> Reporter: Anders Hammar
> Assignee: Anders Hammar
> Attachments: binding-test.zip
>
>
> If a plugin execution binding is declared in pluginManagement it gets bound
> to the build lifecycle in Maven 3.0.x, but not with Maven 2.2.1.
> My understanding is that the behavior in Maven 3.0 is wrong; an execution
> binding needs to be declared in build/plugins/plugin to be bound.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
