[
https://issues.apache.org/jira/browse/MNG-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799278#comment-17799278
]
ASF GitHub Bot commented on MNG-7982:
-------------------------------------
gnodet commented on PR #1357:
URL: https://github.com/apache/maven/pull/1357#issuecomment-1865512751
> 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?
Keeping deployed artifacts consumable by maven 3 is still the plan to day,
and yes, this kinda imply we can't really bring-in things that would require a
change at consumption time in maven 3. However, in Maven 4, the 4.1.0 model
has a flag `preserveModelVersion` which can be used to force the usage of 4.1.0
model at deployment time. This could be used to force the trigger of the new
behaviour on the consumer side, at the cost of requiring maven 4.0.0.
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 ?
> 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)
