Stephane Nicoll created MNG-5971:
------------------------------------
Summary: Dependency management in a child project cannot override
a version using a BOM
Key: MNG-5971
URL: https://issues.apache.org/jira/browse/MNG-5971
Project: Maven
Issue Type: Bug
Components: Dependencies
Affects Versions: 3.3.3
Reporter: Stephane Nicoll
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!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
