Repository navigation
[java] refresh cached Central prefixes - #1542
Merged
Merged
Conversation
An immutable CI archive can retain Maven Central's namespace index from before River's first release. Resolver can reuse that local metadata for the rest of the day, producing a warning that fails every Java build even when the published artifact is available and the build succeeds. Discard only Central's auto-discovered prefix index after restoring the Maven cache and before a Maven build loads it. Fetch current metadata on the next build while retaining dependency artifacts, user-defined filters, and the strict warning policy.
brandur
approved these changes
Oct 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An immutable Maven cache can restore Central's prefix index from before River's namespace was published. Maven can reuse that metadata for the rest of the day, making every Java job fail the strict warning policy even though Resolver verifies the artifact exists and the build succeeds.
Remove only Central's auto-discovered prefix index immediately after cache restore, before a Maven build can load it. The next process downloads current metadata while retaining dependency artifacts, user-defined repository filters, and the existing warning policy.