Repository navigation
ci: Upgrade central-publishing-maven-plugin to 0.12.0 - #84
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
liamhughes
changed the title
liamhughes
commented
Oct 14, 2026
Comment on lines
+74
to
+77
| # Maven Central rejects bundles containing local-repository metadata. | ||
| if unzip -l "$SRC" | grep -E 'maven-metadata-local\.xml|_remote\.repositories'; then | ||
| echo "Error: bundle contains local-repository metadata files"; exit 1 | ||
| fi |
Contributor
Author
There was a problem hiding this comment.
Not sure we really need this, but doesn't hurt.
dylanlerch
approved these changes
Oct 15, 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
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.
Background
Since 7 October, Maven Central has rejected the provider's pre-release bundles. The
ubuntu-latestrunner moved to Maven 3.10.0, and under 3.10central-publishing-maven-plugin0.8.0 stages artifacts with Maven's install mechanism, which now also writesmaven-metadata-local.xmland_remote.repositoriesinto the bundle. Central rejectsmaven-metadata-local.xmlbecause its folder has no.pom.Plugin 0.12.0 fixes the Maven 3.10 bundle bug and adds
skipUpload, which builds the bundle without uploading it. Octopus, not Maven, owns the upload to Central.A version bump alone isn't enough, which is why every build of #34 has failed since July. On newer versions
skipPublishingalso skips staging, so nocentral-bundle.zipis produced and the build fails at "Name the bundle".This supersedes #34.
Part of BMBB-1251.
Changes
central-publishing-maven-pluginfrom 0.8.0 to 0.12.0.<skipPublishing>true</skipPublishing>with<skipUpload>true</skipUpload>.server-id/server-username/server-passwordplaceholders fromsetup-java, and theMAVEN_CENTRAL_*placeholder env vars.skipUploaddoesn't need acentralserver entry.maven-metadata-local.xmlor_remote.repositories, so we catch this before Central does.Testing
settings.xmlserver entry and GPG skipped, produced a 20-file bundle identical to the unsigned file list of the 7 October bundle that validated. CI signs it, which adds 4.ascfiles for 24.