Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.8, 3.0-alpha-1, 3.0
-
Fix Version/s: 2.0.9
-
Component/s: Plugins and Lifecycle
-
Labels:None
-
Number of attachments :
Description
If you build and install a plugin with managed versions that affect plugin transitive dependencies, when it's used the dependency management is ignored
If the dependency management affects the plugin direct dependecies it works properly because the information is merged.
eg.
Plugin A depends on jar B that depends on jar C[1.0]
A dependencyManagement explicitly forces C[2.0], you build and install using C[2.0] in the classpath
If you use plugin A in your pom it will be used with C version 1.0
Attachments
Issue Links
| This issue relates to: | ||||
| MNG-3396 | Managed versions dont affect over constrained ranges |
|
|
|
After fixing
MNG-3396a plugin with over constrained version ranges can be built using depManDue to his bug the plugin can't be used as depMan is ignored
MNG-3396a plugin with over constrained version ranges can be built using depMan Due to his bug the plugin can't be used as depMan is ignored