[
https://issues.apache.org/jira/browse/MNG-8026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810572#comment-17810572
]
ASF GitHub Bot commented on MNG-8026:
-------------------------------------
rmannibucau commented on PR #1391:
URL: https://github.com/apache/maven/pull/1391#issuecomment-1908933445
@cstamas I see the 1-1 with what exists but I have some hard time - blame
the hour maybe ;) - to see how we can make it consistent with the type work
which is pending, typically build path will not be a build path but more a
resolved artifact set totally unrelated to any path now, no? So for me scope
becomes just a resolution stage more than anything else. Am I missing something?
> 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)
