[
https://issues.apache.org/jira/browse/MRESOLVER-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695582#comment-17695582
]
ASF GitHub Bot commented on MRESOLVER-337:
------------------------------------------
cstamas commented on PR #262:
URL: https://github.com/apache/maven-resolver/pull/262#issuecomment-1451559294
In general I like this PR and idea to distinguish "not found remotely" vs
"filtered out" (not even tried remotely)... so I am +1 for this PR but also I'd
like to generally improve overall error reporting of resolver.... but that is
NOT for 1.9.6 but more like 1.10.0
> Real cause when artifact not found with repository filtering
> ------------------------------------------------------------
>
> Key: MRESOLVER-337
> URL: https://issues.apache.org/jira/browse/MRESOLVER-337
> Project: Maven Resolver
> Issue Type: Improvement
> Reporter: Slawomir Jaranowski
> Priority: Major
> Fix For: 1.10.0
>
>
> One case from MRESOLVER-335.
> When we use remote repository filtering real cause for artifact not found may
> be hidden.
> We can return first ArtifactNotFoundException which is not caused by
> filtering.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
