Repository navigation
fix: Pin Maven 3.9.16 so Central accepts the release bundle - #132
Merged
Merged
Conversation
Maven 3.10.0 makes central-publishing-maven-plugin 0.11.0 stage _remote.repositories and maven-metadata-local.xml into the bundle, which Central rejects. Revert the wrapper to 3.9.16 and have dependabot ignore apache-maven >= 3.10.0.
|
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.



Summary
The Release workflow has failed on the last two
masterpushes (v2.11.2, v2.12.0) at the Central upload:Cause: #130 bumped the Maven wrapper 3.9.16 → 3.10.0. With 3.10.0,
central-publishing-maven-plugin0.11.0 (latest) stages_remote.repositories(+ checksums) andmaven-metadata-local.xmlinto the bundle; Central rejects the stray metadata file.org.apache.maven:apache-maven>= 3.10.0 until the plugin supports it.v2.11.2 and v2.12.0 were tagged but never reached Central; the release from this
fix:commit publishes everything since v2.11.1.Verification
Built the bundle locally against a dummy Central endpoint (
-DcentralBaseUrl), same commit, both Maven versions. The only difference is the extra files under 3.10.0:Under 3.9.16 the bundle has only the jar, sources, javadoc and pom with checksums, as in earlier successful releases.