[MNG-3297] maven should not give dependencies to plugins that don't @requireDependencyResolution

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.7
• Fix Version/s: 3.0-alpha-7
• Component/s: Plugins and Lifecycle
• Assignee: Benjamin Bentmann
• Reporter: Brian E Fox
• Created: 21/Nov/07 07:20
• Updated: 10/Mar/16 13:54
• Resolved: 25/Mar/10 11:07

Description

Currently we seem to hand over the dependencies as resolved by the last plugin. This leads to scenarios where sometimes plugins work because they get the right ones but it is subject to break at any time in subtle ways. Therefore, we should give nothing to the plugin so the plugin author will realize the mistake immediately.

Issue Links

• relates to: MNG-1390 @requiresDependencyResolution in process-classes post compile
• relates to: MNG-4526 [regression] Shade plugin includes too much (relative to 2.2.1)
• relates to: MNG-4607 Regression: Maven Android Plugin dependency pull in fails under maven3alpha7
• relates to: MNG-4672 [regression] jnlp doesn't contains dependencies anymore when attaching sources to package phase
• relates to: MNG-3941 Execution project is accessible to later mojo executions