Elliotte Rusty Harold created MNG-8516:
------------------------------------------
Summary: dependencyManagement in a single pom
Key: MNG-8516
URL: https://issues.apache.org/jira/browse/MNG-8516
Project: Maven
Issue Type: Improvement
Components: Documentation: General
Reporter: Elliotte Rusty Harold
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?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
