[jira] [Commented] (MRESOLVER-333) Distinguish better resolver errors for artifact availability

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MRESOLVER-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694500#comment-17694500 ] 

ASF GitHub Bot commented on MRESOLVER-333:
------------------------------------------

cstamas opened a new pull request, #261:
URL: https://github.com/apache/maven-resolver/pull/261

   Users get confused about artifact availability checks, and resolver should provide better error messages. Availability check is checking for (known) origin of locally cached artifact and the request repositories overlap, if none found, the artifact, despite being present locally, is not available.
   
   Present this to end users, and educate them what is and what for is "artifact availability check".
   
   ---
   
   https://issues.apache.org/jira/browse/MRESOLVER-333




> Distinguish better resolver errors for artifact availability
> ------------------------------------------------------------
>
>                 Key: MRESOLVER-333
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-333
>             Project: Maven Resolver
>          Issue Type: Task
>          Components: Resolver
>            Reporter: Tamas Cservenak
>            Priority: Major
>             Fix For: 1.9.6
>
>
> Improve resolver emitted errors to detail more about the state (the error) how resolver came up with it. Example issues:
>  * MNG-5185
>  * MNG-7001
> The "artifact availability check" is widely misunderstood.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)