[
https://issues.apache.org/jira/browse/MNG-8026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810573#comment-17810573
]
ASF GitHub Bot commented on MNG-8026:
-------------------------------------
cstamas commented on PR #1391:
URL: https://github.com/apache/maven/pull/1391#issuecomment-1908946500
It was always "build path" but Maven internally called it wrongly
"classpath" :wink:
Basically what we do here is laying down new API blocks for dep scopes and
build path scopes.
The other PR is about "filling in the properties".
And ultimately, you as for "main-compile" or "test-compile" build path,
Maven calls into Resolver and it resolves those for you, and you end up with a
bunch of artifacts (that are coming via project, so are dependency, hence, had
type).
Then, those collections are "split", filtered by various properties present
in their artifact.properties that makes them "fall" into proper bucket, like
classpath, modulepath, etc
> 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)
