[
https://issues.apache.org/jira/browse/MNG-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067296#comment-15067296
]
Hudson commented on MNG-5359:
-----------------------------
SUCCESS: Integrated in maven-3.x #1183 (See
[https://builds.apache.org/job/maven-3.x/1183/])
[MNG-5359] Declared execution in PluginMgmt gets bound to lifecycle (schulte:
rev d5ba185c1ab926b53acb0947c8a13ad74eac55e6)
*
maven-core/src/main/java/org/apache/maven/lifecycle/internal/DefaultLifecyclePluginAnalyzer.java
*
maven-core/src/main/java/org/apache/maven/lifecycle/internal/DefaultLifecycleMappingDelegate.java
*
maven-core/src/main/java/org/apache/maven/lifecycle/LifecycleMappingDelegate.java
> 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
> Assignee: Christian Schulte
> Fix For: 3.4.0
>
> 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.3.4#6332)
