[
https://issues.apache.org/jira/browse/MRESOLVER-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942044#comment-15942044
]
Christian Schulte commented on MRESOLVER-10:
--------------------------------------------
Issue is fixed in the master branch of [my private maven repository on
github|https://github.com/ChristianSchulte/maven-resolver/tree/master]. When
interested, you can cherry pick the commit to your own repository and create a
pull request for the apache master branch with just this commit yourself from
there.
> New class 'TransitiveDependencyManager' supporting transitive dependency
> management.
> ------------------------------------------------------------------------------------
>
> Key: MRESOLVER-10
> URL: https://issues.apache.org/jira/browse/MRESOLVER-10
> Project: Maven Resolver
> Issue Type: New Feature
> Components: resolver
> Reporter: Christian Schulte
> Priority: Minor
> Fix For: Maven Artifact Resolver 1.2.0 pre-reset
>
>
> 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 new {{TransitiveDependencyManager}} will use that dependency management:
> this new behaviour is expected to be a better choice.
> It could also be named {{DefaultDependencyManager}}, once it is integrated
> into Maven core (version to be defined) as default new behaviour = a
> behaviour that is more predictible/logical, but that will break some
> previously working builds.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
