[
https://issues.apache.org/jira/browse/MNG-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804247#comment-17804247
]
ASF GitHub Bot commented on MNG-7982:
-------------------------------------
cstamas commented on PR #1357:
URL: https://github.com/apache/maven/pull/1357#issuecomment-1880869332
> However, I have no idea what the impact is if one builds a project with
the _transitive_ dependency manager, but uses it with the _classic_ one in
Maven 3. Could that break the consumer side ?
I don't quite understand: so _same project_ that is once built with Maven 4
and once with Maven 3? Or an artifact that is dependency once in Maven4 built
project and once in Maven3 project? Or WDYM?
> 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)
