Repository navigation
fix(java): bump central-publishing-maven-plugin to 0.12.0 for Maven 3.10 - #29
Merged
Merged
Conversation
The ubuntu-latest runner now ships Maven 3.10, which names the staging
metadata file maven-metadata-local.xml and writes _remote.repositories
markers. Plugin 0.11.0 only strips Maven 3.9's maven-metadata-central-staging.xml,
so the bundle reached the Central Portal with a stray file and failed validation
("Bundle has content that does NOT have a .pom file"). 0.12.0 removes all of
them before bundling.
dianadc13
approved these changes
Oct 22, 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.
What
Bumps
central-publishing-maven-pluginfrom 0.11.0 to 0.12.0 (released 2026-10-13). One line injava/pom.xml.Why
The
java-v1.0.0release run (https://github.com/aws/developer-toolkit-elasticache/actions/runs/39800947761) uploaded its bundle but the Central Portal rejected it:The
ubuntu-latestrunner now ships Maven 3.10.0. Maven 3.10 names the staging-repository metadata filemaven-metadata-local.xmland writes_remote.repositoriesmarkers; plugin 0.11.0 only strips Maven 3.9'smaven-metadata-central-staging.xml, so the stray metadata file was bundled at the artifact level and failed validation. Nothing was published; 1.0.0 is still unused.Reproduced locally with Maven 3.10.0 against an unreachable upload URL: the 0.11.0 bundle contains
developer-toolkit-elasticache/maven-metadata-local.xmlplus four_remote.repositories*files. With 0.12.0 the plugin logsPre Bundling - deletedfor the metadata file, the markers and.locks, and the bundle holds only the 20 expected files under1.0.0/. Verified the same with Maven 3.9.16, which keeps working.After merge
Delete the
java-v1.0.0release and tag, recreate them from the newmainhead, and run the release again. The failed deploymentda3f4d5acan be dropped from the Portal's Deployments page or left; it does not block re-uploading 1.0.0.