[MRESOLVER-428] Handle differently the "memoized HTTP 404" cached responses

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Component/s: Resolver
• Assignee: Unassigned
• Reporter: Tamas Cservenak
• Created: 06/Nov/23 17:15
• Updated: 15/Nov/23 10:30
• Resolved: 15/Nov/23 10:30

Description

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

Issue Links

• is fixed by: MNG-7935 Expose "cache not found artifacts" configuration