You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2023/11/21 11:05:00 UTC
[jira] [Assigned] (MNG-7935) Expose "cache not found artifacts" configuration
[ https://issues.apache.org/jira/browse/MNG-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tamas Cservenak reassigned MNG-7935:
------------------------------------
Assignee: Tamas Cservenak
> Expose "cache not found artifacts" configuration
> ------------------------------------------------
>
> Key: MNG-7935
> URL: https://issues.apache.org/jira/browse/MNG-7935
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-9
>
>
> By default Maven caches "not found artifacts", the well known "was not found in ... during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until..." error. Only escape route is either wait for update interval, or, use {{-U}} that in turn, refreshes whole universe.
> We should be able to turn off "not found artifact" caching.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)