Tamas Cservenak created MRESOLVER-555:
-----------------------------------------
Summary: Existence check should lax the repository update policy
Key: MRESOLVER-555
URL: https://issues.apache.org/jira/browse/MRESOLVER-555
Project: Maven Resolver
Issue Type: Bug
Components: Resolver
Reporter: Tamas Cservenak
Fix For: 2.0.0, 2.0.0-beta-1
Maybe only when update policy is "never".
Order of events:
* attempt a build with not-yet-released-artifact (for example resolver in
maven)
* as it is not in central, build will fail, and central URL will be "cached"
as 404
* fix, rinse, repeat, add staging repository, rebuild
* build will pass ok, as staging repository will have the artifact, it is
cached to local repository (from staging repository)
* later, staging repository is dropped, release promoted to central.
* rebuild: here, Resolver will nag that "artifact is present but not
available", which is true: it was cached from staging repository
* it will go try to see is it available in central (existence check), but:
central has 404 cached (see step 1), and in this case update policy is being
obeyed, that is "never"
* due "never" update policy existence check will fail, and build will fail
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
