[
https://issues.apache.org/jira/browse/MNG-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16307098#comment-16307098
]
ASF GitHub Bot commented on MNG-5359:
-------------------------------------
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven-integration-testing/pull/27
[MNG-5359] Declared execution in PluginMgmt gets bound to lifecycle (…
…regression)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ChristianSchulte/maven-integration-testing
MNG-5359
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-integration-testing/pull/27.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #27
----
commit dcbc5b2634cf1fe00afeaa43391dc6543736f6d4
Author: Christian Schulte <schulte@...>
Date: 2015-12-20T18:34:40Z
[MNG-5359] Declared execution in PluginMgmt gets bound to lifecycle
(regression)
----
> Declared execution in PluginMgmt gets bound to lifecycle (regression)
> ---------------------------------------------------------------------
>
> Key: MNG-5359
> URL: https://issues.apache.org/jira/browse/MNG-5359
> Project: Maven
> 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
> Fix For: 3.5.x-candidate
>
> Attachments: MNG-5359-IT.patch, 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 was sent by Atlassian JIRA
(v6.4.14#64029)
