You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2019/06/08 17:54:00 UTC

[jira] [Closed] (MRESOLVER-33) New 'DefaultDependencyManager' managing dependencies on all levels supporting transitive dependency management

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

Michael Osipov closed MRESOLVER-33.
-----------------------------------
    Resolution: Fixed

Fixed with [a9f849c59e5fa774ebc88df4cfccb293c28fbc09|https://gitbox.apache.org/repos/asf?p=maven-resolver.git;a=commit;h=a9f849c59e5fa774ebc88df4cfccb293c28fbc09].

> New 'DefaultDependencyManager' managing dependencies on all levels supporting transitive dependency management
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: MRESOLVER-33
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-33
>             Project: Maven Resolver
>          Issue Type: New Feature
>            Reporter: Christian Schulte
>            Assignee: Michael Osipov
>            Priority: Trivial
>             Fix For: 1.4.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The {{ClassicDependencyManager}} ignores the dependency management from transitive dependencies to maintain backwards compatibility with Maven 2, then Maven 3 (objective when extracting Aether was to keep compatibility).
> The {{TransitiveDependencyManager}} will use that dependency management and will still support management overrides from inside {{<dependencies>}} elements. See the linked issues.
> The {{DefaultDependencyManager}} will no longer support such overrides and can be considered the default implementation from a resolver point of view.



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