[
https://issues.apache.org/jira/browse/MRESOLVER-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17904129#comment-17904129
]
Konrad Windszus commented on MRESOLVER-633:
-------------------------------------------
Seems that the meta information from which remote repository the artifact was
tried to be retrieved is captured in the meta data file
{{<artifactName>.lastUpdated}}.
> Clarify caching of 404 responses on artifact resolving in local repository
> --------------------------------------------------------------------------
>
> Key: MRESOLVER-633
> URL: https://issues.apache.org/jira/browse/MRESOLVER-633
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
> Reporter: Konrad Windszus
> Priority: Major
>
> A dedicated section in
> https://maven.apache.org/resolver/local-repository.html about local caching
> of unresolvable artifacts would be beneficial.
> IIUC it respects the update policy and all files not found in any remote repo
> are stored as 0 byte artifacts in the local repo.
> It is unclear to me how to deal with edge cases like adding a new repo which
> provides that previously unresolvable release artifact? What do I need to do
> from a consumer perspective to resolve that, if the 0 byte artifact is
> already cached in the local repo....
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
