[jira] [Moved] (MNGSITE-367) Document how versions of a direct dependency's transitive dependencies are selected.

["Karl Heinz Marbaise (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MNGSITE-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Heinz Marbaise moved MNG-6621 to MNGSITE-367:
--------------------------------------------------

    Component/s:     (was: Documentation:  General)
            Key: MNGSITE-367  (was: MNG-6621)
        Project: Maven Project Web Site  (was: Maven)

> Document how versions of a direct dependency's transitive dependencies are selected. 
> -------------------------------------------------------------------------------------
>
>                 Key: MNGSITE-367
>                 URL: https://issues.apache.org/jira/browse/MNGSITE-367
>             Project: Maven Project Web Site
>          Issue Type: Improvement
>            Reporter: Elliotte Rusty Harold
>            Priority: Major
>
> Situation:
> a:a depends on foo:foo:2.1
> foo:foo:2.1 depends on baz:baz:3.2
> baz:baz:3.2 depends on guava:guava:25.0-android
> However, foo:foo:2.1 imports a BOM (or inherits from a parent pom) that specifies that guava:guava:27.1-jre will be used.
> So which version of guava:guava does a:a add to its classpath, 25.0-android or 27.1-jre? I think the answer is 25.0-android. That is, the dependency management from the middle of the tree is ignored when building a:a. 
> However I don't think the docs ever say this. They need to. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)