[
https://issues.apache.org/jira/browse/MNG-8026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810816#comment-17810816
]
ASF GitHub Bot commented on MNG-8026:
-------------------------------------
cstamas commented on PR #1391:
URL: https://github.com/apache/maven/pull/1391#issuecomment-1909896797
> Maybe, but there's no point in the first PR if we don't go further...
Um, the point of first commit is to move off from all the deprecated classes
in resolver (see https://github.com/apache/maven-resolver/pull/412 and related
JIRA), as currently, boundary of "scope interpretation and transformation" is
completely blurred and doubled between Resolver and Maven Core. Things like
adding new scopes is not trivial at all, as it requires changes in both
projects, whereis Resolver should be really oblivious about scopes.
The first commit is really not related to 2nd step, it just does the right
thing (moves all scope related logic to Maven Core), that in turn also
effectively clears grounds for step2.
> 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)
