Project

General

Profile

Actions

Bug #12834

closed

We need to explicit version of scala-library in plugin-parent else one is pick at random from transitive dependencies

Added by François ARMAND over 6 years ago. Updated over 6 years ago.

Status:
Released
Priority:
N/A
Category:
Architecture - Dependencies
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

I definitly stop to try to understand how maven works.

So, for most dependencies, if you put them in "dependencyManagement" with scope "provided" but without version, maven takes the version in other Rudder project. But not for scala-library, where it seems to take the one from liftweb.

So in fact, I believe I just don't understand anything, and that maven just takes the first transitive dep it get, even if it's 4 version below other ones. Putting the verison in dependencyManagement does not seem to solve the problem (ie: if the version is in dependencyManagement, it does not affect transitive dependency resolution, so you need to put the dependency as a dependency (even if you keep version in dependencyManagmeent) to have the correct version resolved. This is madness).

I declare forfeit and start to read documentation about Bazel and Mill.

Actions

Also available in: Atom PDF