[ https://issues.apache.org/jira/browse/MRESOLVER-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17786296#comment-17786296 ]
Tamas Cservenak commented on MRESOLVER-428: ------------------------------------------- Created Maven issues: https://issues.apache.org/jira/browse/MNG-7935 https://issues.apache.org/jira/browse/MNG-7936 And am closing (and moving out) this issue from Resolver 2.0.0. > 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)