[MNG-6284] <executions> inside <pluginManagement> should raise a warning

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 3.0.5
• Environment: Ubuntu 14.04.3
• Assignee: Unassigned
• Reporter: Chris Hennick
• Created: 15/Sep/17 06:38
• Updated: 29/Jan/18 10:16
• Resolved: 29/Jan/18 10:14

Description

When I was setting up my project's pom.xml, I was unaware that there was a difference between project/build/pluginManagement/plugins and project/build/plugins. These StackOverflow questions indicate I'm not the only one who was confused:

• https://stackoverflow.com/questions/18557245/not-able-to-bind-plugin-goals-to-maven-lifecycle-phases
• https://stackoverflow.com/questions/23785443/binding-to-lifecycle-in-maven-does-not-work-on-failsafe-and-integration-test

If we have to have such a confusing schema, then can we please at least raise a warning when the confusion inevitably occurs, given how easy it is to detect (since AFAICT there'd be no reason to put an executions tag inside pluginManagement/plugins/plugin)?

Issue Links

• is caused by: MNG-5359 Declared execution in PluginMgmt gets bound to lifecycle (regression)