Repository navigation
Bump central-publishing-maven-plugin to 0.12.0 so releases build a valid bundle - #18
Merged
Merged
Conversation
…lid bundle GitHub's ubuntu-24.04 runner image moved its Maven from 3.9.16 to 3.10.0 in its 20261004 release. Under Maven 3.10.0, plugin 0.11.0 stages Maven's local-repository files (maven-metadata-local.xml next to the version directory, and _remote.repositories beside the artifacts) into the Central bundle, and the Central Portal refuses the deployment: "Bundle has content that does NOT have a .pom file: com/millionsend/millionsend-java". With 0.12.0 the bundle holds only the jar, sources, javadoc and pom (with their signatures and checksums) under both Maven 3.9.16 and 3.10.0, checked by building the release bundle with each. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
The v0.9.0 release never reached Maven Central: the Central Portal refused the deployment with
GitHub's ubuntu-24.04 runner image moved its Maven from 3.9.16 to 3.10.0 (image release 20261004). Under Maven 3.10.0, central-publishing-maven-plugin 0.11.0 stages Maven's local-repository files into the bundle:
maven-metadata-local.xmlnext to the version directory, and_remote.repositoriesbeside the artifacts. 0.8.0 was released before the image change, so it went through.Checks
The release bundle was built locally with
-P release, with the upload pointed at a closed port, under each Maven version:maven-metadata-local.xml+_remote.repositoriesA clean bundle holds the jar, sources, javadoc and pom with their checksums (signatures too in a signed release).
After merge
Dispatch the Release workflow from
mainto publish 0.9.0.mainis the v0.9.0 tag plus this commit.🤖 Generated with Claude Code