[ 
https://issues.apache.org/jira/browse/MNG-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16307102#comment-16307102
 ] 

ASF GitHub Bot commented on MNG-5359:
-------------------------------------

Github user ChristianSchulte commented on the issue:

    https://github.com/apache/maven-integration-testing/pull/27
  
    [Corresponding Maven pull 
request.](https://github.com/apache/maven/pull/143)


> 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)

Reply via email to