[MNG-5971] Imported dependencies should be available to inheritance processing

• Type: Bug
• Status: Reopened
• Priority: Trivial
• Resolution: Unresolved
• Affects Version/s: 3.3.3
• Fix Version/s: 4.0.x-candidate
• Component/s: Dependencies
• Assignee: Unassigned
• Reporter: Stephane Nicoll
• Created: 02/Feb/16 09:56
• Updated: 27/Jul/23 07:01

Description

When a project extends from a parent with a dependencyManagement section, it is not always possible to properly override (and align) the version to use for a group of dependencies.

We typically use Bill Of Materials to gather a group of modules and make sure their versions are consistent.

The following project demonstrates the issue: https://github.com/snicoll-scratches/maven-dependency-management

The first commit is a working use case where the parent uses a bom with version A and we use the same bom with version B in the child. Version B is used as expected.

The second commit demonstrates the faulty scenario. Rather than using a bom in the parent, we use a direct dependency (provided by that bom). We still use the bom with a different version. In that case all the dependencies but the one provided by the parent are overridden (leading to mixed versions for the dependencies provided by the BOM).

It looks like the distance is still used to compute the version while the graph of dependencies should be flatten at each step for a proper override.

Thoughts? Thanks!

Issue Links

• is duplicated by: MNG-5547 import scope of dependencyManagement doesn't seem to work
• is duplicated by: MNG-5947 dependencyManagement import section does not resolve dependencies using "nearest" definition
• is duplicated by: MNG-6246 Inconsistent override behaivor with BOM vs dependency
• is duplicated by: MNG-6161 Dependencies' management via <scope>import</scope> should take precedence over inherited definitions
• relates to: MNG-5947 dependencyManagement import section does not resolve dependencies using "nearest" definition
• relates to: MNG-5982 The POM for ... is invalid, transitive dependencies ... while property was overriden
• relates to: MNG-7852 Use all the versions for dependency resolution rather than "nearest first" or "declared first"
• supercedes: MNG-6079 3.4 regression: cannot override version of a dependencyManagement in a submodule any more
• mentioned in: Page Loading...