[
https://issues.apache.org/jira/browse/MNG-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799137#comment-17799137
]
ASF GitHub Bot commented on MNG-7982:
-------------------------------------
rmannibucau commented on PR #1357:
URL: https://github.com/apache/maven/pull/1357#issuecomment-1864990604
Hmm, still thinking a bit out loud but at some point it was discussed that
the consumed pom would be "cleaned for central" (flatten maven plugin like etc)
to ensure the consumers see it as the producer in terms of resolution, whatever
version it uses, is it still in the scope? If so depMgt is maybe no more a
thing transitively and then we just do what we want for maven 4, wdyt?
> Switch to enable transitivity in depMgr used by Maven
> -----------------------------------------------------
>
> 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).
> Resolver MRESOLVER-462 that is a boolean switch (to enable or disable -- as
> before -- the transitivity in depMgr).
> This depends on resolver release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
