[
https://issues.apache.org/jira/browse/MRESOLVER-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695339#comment-17695339
]
Tamas Cservenak commented on MRESOLVER-337:
-------------------------------------------
A very good initiative. I have several issues with ArtifactResolutionException
and it's "twin"
DependencyResolutionException, especially around this, that it sometimes
reports only one cause...
Given the class receive List<ArtifactResult> the output should be more like
this:
{noformat}
G1:A1:V1 (absent) repo1: not found
repo2: filtered out
repo3: not found
G2:A2:V2 (absent): repo1: not found
...{noformat}
basically, the exception receives a list of ArtifactResult, where each result
contains one or more exceptions, and many times error IS misleading. Just try
to use 2 or more remote repositories (so define some plus), and it will say
"not available from repo1"... was repo2 tried at all?
> 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
>
> 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)
