[MNG-5359] Declared execution in PluginMgmt gets bound to lifecycle (regression)
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 297
Description
**[Anders Hammar](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=afloom)** opened **[MNG-5359](https://issues.apache.org/jira/browse/MNG-5359?redirect=false)** and commented
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.
---
**Affects:** 3.0.1, 3.0.2, 3.0.3, 3.0.4
**Attachments:**
- [binding-test.zip](https://issues.apache.org/jira/secure/attachment/12713110/binding-test.zip) (_5.17 kB_)
- [MNG-5359-IT.patch](https://issues.apache.org/jira/secure/attachment/12712701/MNG-5359-IT.patch) (_5.64 kB_)
**Issue Links:**
- [MNG-6284](https://issues.apache.org/jira/browse/MNG-6284) \ inside \ should raise a warning
(_**"causes"**_)
**Remote Links:**
- [Page
](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67636510)
- [GitHub Pull Request #27
](https://github.com/apache/maven-integration-testing/pull/27)
- [GitHub Pull Request #143
](https://github.com/apache/maven/pull/143)
- [GitHub Pull Request #27
](https://github.com/apache/maven-integration-testing/pull/27)
0 votes, 7 watchers
Contributor guide
Assessment
This issue has not been assessed yet.