[
https://issues.apache.org/jira/browse/MNG-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805563#comment-17805563
]
ASF GitHub Bot commented on MNG-7982:
-------------------------------------
cstamas commented on PR #1357:
URL: https://github.com/apache/maven/pull/1357#issuecomment-1887094814
> I mean you build the project with maven 4, upload to central, and a maven
3 projects depends on it.
Yes, in that case they may be differences. BUT, since we talk about _two
distinct projects_: your, that is built with mvn4, and theirs (consumer) built
with mvn3. So they will anyway have more dependencies, not just your lib, and
they will anyway have to handle their transitive hull, hence _maybe_ will need
to have more entries in their depMgt to make things work out for them. Just
like things worked so far, no change here.
In general, I don't see this as an issue at all, here is why: consumer
either suffered from issue like https://issues.apache.org/jira/browse/MNG-7003
and they had it fixed, or they do not suffer from this issue.
I see this just like making maven "more correct", "more convergent", am
pretty much sure we do not _break anything_ with this.
> 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-11
>
>
> 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)
