[
https://issues.apache.org/jira/browse/MRESOLVER-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783293#comment-17783293
]
Christoph Läubrich commented on MRESOLVER-428:
----------------------------------------------
Would be great if such a 404 is simply retried on next maven invocation, as
user will see error and act on it (e.g. fix network settings, add repository,
fix typo) and then retry to see everything works.
Currently then user get *another error* and is confused how to fix that.
Also very common case is when there is a new release and one is to eager to try
it out, get 404 because it is not (yet) synced, leaving all kind of strange
errors after the next run when it is there forcing to use -U to fix that up...
> 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)
