[
https://issues.apache.org/jira/browse/MNG-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799002#comment-17799002
]
ASF GitHub Bot commented on MNG-7982:
-------------------------------------
cstamas commented on PR #1357:
URL: https://github.com/apache/maven/pull/1357#issuecomment-1864456808
This setting cannot be per dependency, at least resolver does not support
that. The depMgr is set per session. And what current PR changes is really only
this: are depMgt sections obeyed only 2 level deep or to the end of pit. The "2
level depth" comes from Maven2 times, and was artificial limit just to make
Maven3 (resolver in it) work like Maven2 did. Unsure why Maven4 would need to
work in this respect as Maven2 did.
> Make classic transitive depMgr the default, provide fallback to classic and
> transitive
> --------------------------------------------------------------------------------------
>
> Key: MNG-7982
> URL: https://issues.apache.org/jira/browse/MNG-7982
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-12
>
>
> As seen in various issues (MRESOLVER-235, MNG-7003 and others), users are
> calling out how depMgt should be handled in both cases: when building (it
> is), and when consuming (it is not).
> As it turned out, Maven3 since existence of Resolver used the "classic"
> depMgr that works like Maven2 (does not apply depMgt). Maven4 may be point to
> apply "transitive" depMgr as default, while offer fallback to classic?
> This depends on resolver release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
