[
https://issues.apache.org/jira/browse/MNG-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799000#comment-17799000
]
ASF GitHub Bot commented on MNG-7982:
-------------------------------------
rmannibucau commented on PR #1357:
URL: https://github.com/apache/maven/pull/1357#issuecomment-1864449457
What I worry about it is the fact we are moving the current issues a step
further but I don't understand yet how it does fix anything, this kind of
configuration looks per dependency, so while I fully agree we can make it
global or per version, it will keep blowing up as soon as you have > 2 dep
there no?
Don't get me wrong, I think the transitive feature is rather a good thing if
we can instantiate it without more side effects than we have today but alone it
looks like mixing behaviors which all have pitfalls and therefore just make it
more complex.
Ultimately it can mean we become stricter on the depMgt and forbid not
resolved conflicts (a bit like what enforcer plugin enables), this way the
resolution of a built project (not transitive deps alone) is always
deterministic at a little user cost.
Still thinking out loud to try to get this feature onboard without realizing
in some months we are back where we were in terms of issues with new ones due
to the behavior change and "resolution merge" logic we would need from consumed
poms.
> 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)
