[
https://issues.apache.org/jira/browse/MNG-8026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810876#comment-17810876
]
ASF GitHub Bot commented on MNG-8026:
-------------------------------------
cstamas commented on PR #1391:
URL: https://github.com/apache/maven/pull/1391#issuecomment-1910189997
Just a general remark: Am fine if we "redefine" here everything, from ground
up, but IMHO "safest" would be to go "resolver way" (adhere to its abstractions
closest as possible) as it is proven and works. And then improve it from there
(consider "resolver way" as starting point), instead to try to come up with
something completely new and different, and risk the problem of something (some
use case, edge case) being forgotten, and then go thru pain of "fixing it" in
upcoming API versions...
> 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)
