[
https://issues.apache.org/jira/browse/MRESOLVER-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783301#comment-17783301
]
Christoph Läubrich commented on MRESOLVER-428:
----------------------------------------------
I just wanted to add a real use case where it is not the users-fault, of cause
the same can happen when I use an unreleased version once and try to use it
*after* it is really released... bottom line is that usually when I run the
build I do it because I think I have done things right or fixed something,
running a failed build faster (=with cached error) is almost never what I
want...
> Handle differently the "memoized HTTP 404" cached responses
> -----------------------------------------------------------
>
> Key: MRESOLVER-428
> URL: https://issues.apache.org/jira/browse/MRESOLVER-428
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0
>
>
> Currently, mvn local repo will "remember" that a repo reported 404 for
> artifact not present, and this fact is cached using ordinary update policy.
> To make mvn retry, -U is needed, that again, is too heavy handed, as it will
> force update always policy for everything...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
