Details
-
Bug
-
Status: Reopened
-
Critical
-
Resolution: Unresolved
-
3.2.5
-
None
Description
A detailed description of the issue is here:
The short of it is that maven appears to be using the wrong <dependencyManagement> version in a transitive dependency. There are two relevant <dependencyManagement> sections in the build, one pulled in by guice and one pulled in by gwizard-parent. These are the dependency paths from the top:
gwizard-example -> gwizard-config -> gwizard-parent
gwizard-example -> gwizard-config -> guice -> guice-parent
gwizard-parent's dependencyManagement specifies guava 18
guice-parent's dependencyManagement specifies guava 16
Guava 16 is winning. This seems highly undesirable, and in fact it breaks our build. I would expect that in a version # fight, "closest to the top" should win.
Attachments
Attachments
Issue Links
- causes
-
FLINK-9091 Failure while enforcing releasability in building flink-json module
-
- Closed
-
- duplicates
-
MNG-3890 Transitive dependencies override explicitly set scope.
-
- Closed
-
- is blocked by
-
MRESOLVER-10 New 'TransitiveDependencyManager' supporting transitive dependency management
-
- Closed
-
-
MNG-6056 Implement Feature Toggle Module to handle Feature Toggles
-
- Closed
-
- is duplicated by
-
MNG-5769 Maven is ignoring dependencyManagement for transitive dependencies
-
- Closed
-
- is related to
-
MNG-7982 Switch to enable transitivity in depMgr used by Maven
-
- Closed
-
- is required by
-
MNG-6139 Addition of command line option 'legacy-dependency-management'.
-
- Closed
-
- relates to
-
MNG-7003 Inconsistent dependency tree
-
- Closed
-
- mentioned in
-
Page Loading...