Make Central metadata look like mirror metadata [MERGEOK]#37307
Merged
Conversation
When building the offline Maven repository for the system-test container, artifacts resolved directly from Maven Central produce metadata files named maven-metadata-central.xml (plus .sha1/.md5 checksums). Inside the container Maven resolves against the bundled repo as if from a mirror, where the metadata is expected to be named maven-metadata.xml. Copy each maven-metadata-central.xml* file to its maven-metadata.xml* counterpart so the metadata is found regardless of whether the original artifact came from Central or a mirror, avoiding re-downloads.
esolitos
changed the title
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
2 participants
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.
When building the offline Maven repository for the system-test container, artifacts resolved directly from Maven Central produce metadata files named maven-metadata-central.xml (plus .sha1/.md5 checksums). Inside the container Maven resolves against the bundled repo as if from a mirror, where the metadata is expected to be named maven-metadata.xml. Copy each maven-metadata-central.xml* file to its maven-metadata.xml* counterpart so the metadata is found regardless of whether the original artifact came from Central or a mirror, avoiding re-downloads.