Konrad Windszus created MRESOLVER-633:
-----------------------------------------
Summary: 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
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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
