[
https://issues.apache.org/jira/browse/MNG-8026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810830#comment-17810830
]
ASF GitHub Bot commented on MNG-8026:
-------------------------------------
cstamas opened a new pull request, #1392:
URL: https://github.com/apache/maven/pull/1392
Maven should be fully in control regarding dependency scope definitions and
their interpretations (and transformations).
This PR makes following changes:
* no change in behaviour (all works as before), but
* maven codebase contains now all the code related to scopes
* no resolver code is in use (that was deprecated as it was wrong to have it
in resolver, see issue
[MRESOLVER-471](https://issues.apache.org/jira/browse/MRESOLVER-471))
---
https://issues.apache.org/jira/browse/MNG-8026
> 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)
