[jira] [Comment Edited] (MRESOLVER-428) Handle differently the "memoized HTTP 404" cached responses

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

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

Tamas Cservenak edited comment on MRESOLVER-428 at 11/15/23 10:23 AM:
----------------------------------------------------------------------

This is not a resolver issue, resolver already have all bits in place to be configured for things like this.
This is more a Maven issue that can be done as this: https://github.com/apache/maven/commit/e93bb7293792cd68569060b51074b95d6ccb795a


was (Author: cstamas):
This is not a resolver issue, resolver already have all bits in place to be configured.
This is more a Maven issue that can be done as this: https://github.com/apache/maven/commit/e93bb7293792cd68569060b51074b95d6ccb795a

> 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)