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 11:44:00 UTC
[jira] [Updated] (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 updated MRESOLVER-33:
------------------------------------
Summary: New 'DefaultDependencyManager' managing dependencies on all levels supporting transitive dependency management (was: New class 'DefaultDependencyManager' managing dependencies on all levels supporting transitive dependency management.)
> 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
> Priority: Trivial
> Fix For: version-next
>
>
> 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)