Details
-
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
-
Labels:None
-
Number of attachments :
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-4672
[regression] jnlp doesn't contains dependencies anymore when attaching sources to package phase
-
-
MNG-1390
@requiresDependencyResolution in process-classes post compile
-
-
MNG-4526
[regression] Shade plugin includes too much (relative to 2.2.1)
-
-
MNG-4607
Regression: Maven Android Plugin dependency pull in fails under maven3alpha7
-
-
MNG-3941
Execution project is accessible to later mojo executions
-