[ 
https://issues.apache.org/jira/browse/MNG-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17798998#comment-17798998
 ] 

ASF GitHub Bot commented on MNG-7982:
-------------------------------------

gnodet commented on PR #1357:
URL: https://github.com/apache/maven/pull/1357#issuecomment-1864442381

   > Hi @cstamas , what is the plan to identify mvn 4 consumed artifacts to 
switch the impl, using the mvn4 specific pom metadata file? in current state it 
breaks probably too easily IMHO and I didn't find how we enable this behavior 
in the produced pom for the consumed artifact - I don't think it is good to be 
a config prop, it should belong to the pom only to avoid a global toggle which 
will work only under a closed ecosystem.
   
   The consumer has no knowledge.  I also kinda saw that as a problem...
   I wonder if this should be automatically toggled by the modelVersion of the 
root project: if using a 4.1.0 model, then use the new depMgr, if using 4.0.0 
model, use the Maven 3 compatible one....
   This piece can be easily detected very early at boot time and could be used 
to configure the resolver.




> 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)

Reply via email to