[MNG-8516] dependencyManagement in a single pom
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 297
Description
**[Elliotte Rusty Harold](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=elharo)** opened **[MNG-8516](https://issues.apache.org/jira/browse/MNG-8516?redirect=false)** and commented
https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management describes putting a dependencyManagement section in a parent pom, but what about putting a
dependencyManagement section in the current pom.xml? Does this override dependency versions in transitive dependencies?
E.g. suppose my project depends on spring 2.5 which depends on Guava 25.0. If I dependency manage Guava to 33.0, is that now the version that is added to my classpath?
if yes, document this use.
If no, why not?
---
No further details from [MNG-8516](https://issues.apache.org/jira/browse/MNG-8516?redirect=false)
Contributor guide
Assessment
This issue has not been assessed yet.