[jira] [Commented] (MRESOLVER-91) Error messages not clear when not reattempting resolution when a previous attempt failed and the failure was cached

["Hudson (Jira)" <ji...@apache.org>]

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

Hudson commented on MRESOLVER-91:
---------------------------------

Build succeeded in Jenkins: Maven TLP » maven-resolver » master #87

See https://builds.apache.org/job/maven-box/job/maven-resolver/job/master/87/

> Error messages not clear when not reattempting resolution when a previous attempt failed and the failure was cached
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRESOLVER-91
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-91
>             Project: Maven Resolver
>          Issue Type: Improvement
>            Reporter: Giorgos Gaganis
>            Assignee: Michael Osipov
>            Priority: Major
>
> Error messages not clear when not reattempting resolution when a previous attempt  failed and the failure was cached.
> We have experienced the following error message 
> {code:java}
> Failure to find groupid:artifactid:0.0.1 in http://therepo/path/repo was cached in the local repository, resolution will not be reattempted until the update interval of TheRepo has elapsed or updates are forced -> [Help 1]{code}
> At the time we have found this error message to be confusing, we couldn't really understand what was happening. In our case while we had a simple error in our repo configuration we were misled by this message and looking for the problem in our local repository caching.
> During jcrete hackday I was still confused by this but decided to look into it and this led me to the code where I found the description of the mechanism in org.eclipse.aether.resolution.ResolutionErrorPolicy. After reading the javadoc and understanding the mechanism actually the error message makes absolute sense.
> So we might be able to improve the error message so it conveys better what is happeing for users seeing this for the first time and not being aware or understading the failure caching mechanism.
> I will attach a PR with a recommendation for better error messages. With this wording we convey better what has happened before, what exactly was cached from before and why we are currently failing(by not reattempting). 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)