[
https://issues.apache.org/jira/browse/MNG-8026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810691#comment-17810691
]
ASF GitHub Bot commented on MNG-8026:
-------------------------------------
rmannibucau commented on PR #1391:
URL: https://github.com/apache/maven/pull/1391#issuecomment-1909427969
@cstamas does it mean we should fix the naming for mvn 4 and align it on
what it is? Resolverpaths or alike since it is unrelated to any actual build
and becomes even more ambiguous with jpms?
> Maven should define from ground up scopes used with Resolver
> ------------------------------------------------------------
>
> Key: MNG-8026
> URL: https://issues.apache.org/jira/browse/MNG-8026
> Project: Maven
> Issue Type: Task
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-13
>
>
> See MRESOLVER-471, it is actually role of Maven (as a resolver consumer
> project) to define all these things:
> * supported scopes
> * transformations of scopes to build path scopes
> * fine tune conflict resolution and related things (in session)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
