Skip to content

fix(java): central-publishing-maven-plugin 0.12.0 so Maven 3.10 staging metadata stays out of the bundle #451

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dmealing merged 3 commits into from
Oct 23, 2026
Merged

fix(java): central-publishing-maven-plugin 0.12.0 so Maven 3.10 staging metadata stays out of the bundle #451

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3881ac2
fix(java): central-publishing-maven-plugin 0.12.0 so Maven 3.10 stagi…
dmealing Oct 23, 2026
bf2aa35
docs(releasing): note runner Maven version drift and the missing-.pom…
dmealing Oct 23, 2026
32c423e
docs(releasing): name the runner label and the confirming release
dmealing Oct 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -852,6 +852,13 @@ versioned on its own major line — npm major + 7, so `7.x` while npm was `0.x`
> failed with `Polling for … timed out before the deployment completed`, yet 8.0.11 is on
> Central (HTTP 200). Check Central with the loop above before any re-run: a re-run of a
> published version fails as a duplicate.
>
> **The runner's Maven version can change under the workflow.** `java-v8.1.0` was rejected with
> `Bundle has content that does NOT have a .pom file`: the `ubuntu-latest` (24.04) image (2026-10-12 and
> later) ships Maven 3.10.0, which writes `maven-metadata-local.xml` into the install target, and
> `central-publishing-maven-plugin 0.11.0` left it in the staged bundle. Fixed in plugin `0.12.0` (`8.1.0` published with it);
> if that signature returns, inspect the bundle for `maven-metadata-local.xml` and check the
> runner's `mvn -v` before suspecting the poms.

**The `minor.patch` is CONVERGENT across languages, not lockstepped** (standing policy since
0.25.0): npm, PyPI and NuGet share one `major.minor.patch` and Maven Central takes the same
Expand Down
2 changes: 1 addition & 1 deletion server/java/pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -465,7 +465,7 @@
<plugin>
<groupId>org.sonatype.central</groupId>
<artifactId>central-publishing-maven-plugin</artifactId>
<version>0.11.0</version>
<version>0.12.0</version>
<extensions>true</extensions>
<configuration>
<publishingServerId>central</publishingServerId>
Expand Down
Loading