[
https://issues.apache.org/jira/browse/MRESOLVER-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17816938#comment-17816938
]
ASF GitHub Bot commented on MRESOLVER-494:
------------------------------------------
cstamas commented on PR #428:
URL: https://github.com/apache/maven-resolver/pull/428#issuecomment-1940938089
> @cstamas Here's what I have in mind:
[gnodet@791c07e](https://github.com/gnodet/maven-resolver/commit/791c07e3fc05a86fa383607d28db0dcdf7fcc995)
The local path is only managed by the scope handler. The assumption is that
for a given artifact, if it has a system scope, it also has a local path. Maybe
I'm missing something though ...
You do: i.e. you have a dep w/o scope, but you define a depMgr w/ system
scope (and system path), who will apply then that mgmt onto dependency? Also,
this may come from n-th level now, as we introduced "transitive depmgr" etc.
> LOCAL_PATH Artifact property really belongs to "system" scope (or is at least
> very related to it)
> -------------------------------------------------------------------------------------------------
>
> Key: MRESOLVER-494
> URL: https://issues.apache.org/jira/browse/MRESOLVER-494
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0-alpha-8, 2.0.0
>
>
> LOCAL_PATH Artifact property really belongs to "system" scope (or is at least
> very related to it).
> It may need to be removed as well?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
