Repository navigation
[#325] Fix Maven Central release: pin Maven 3.9.16, bump central-publishing to 0.11.0 - #324
Merged
vharseko merged 1 commit intoOct 11, 2026
Conversation
…to 0.11.0 Maven 3.10 on the runner leaves maven-metadata-local.xml and _remote.repositories files in the central-publishing staging directory. They end up in central-bundle.zip, and Maven Central rejects the 3.2.1 deployment with "Bundle has content that does NOT have a .pom file". Install Maven 3.9.16 (sha512-verified) before the release so the bundle stays clean. Also bump central-publishing-maven-plugin from 0.8.0 to 0.11.0. 0.11.0 alone does not fix the Maven 3.10 issue.
vharseko
added
dependencies
4 tasks
vharseko
changed the title
This was referenced Oct 11, 2026
vharseko
added a commit
to OpenIdentityPlatform/OpenAM
that referenced
this pull request
Oct 11, 2026
…to 0.11.0 (#1165) Refs OpenIdentityPlatform/commons#325 (workaround only, the issue stays open) ## Problem Since the `ubuntu-24.04` runner image 20261004 replaced the system Maven 3.9.x with 3.10.0, releases to Maven Central fail in validation: ``` Bundle has content that does NOT have a .pom file: <every artifact directory> ``` Under Maven 3.10, `central-publishing-maven-plugin` leaves local-repository files in its staging directory, and they end up in `central-bundle.zip`: - `maven-metadata-local.xml` in every artifact directory - `_remote.repositories` (+ checksums) in every version directory This first hit OpenIdentityPlatform/commons in release run [38121296549](https://github.com/OpenIdentityPlatform/commons/actions/runs/38121296549). The commons issue has the local reproduction and the upstream links. Plugin 0.8.0 and 0.11.0 behave the same. ## Changes Same workaround as OpenIdentityPlatform/commons#324: - `release.yml`: before the release, install Maven 3.9.16 from `archive.apache.org` with a pinned sha512 and put it first on `PATH`. `release:perform` runs its nested build with the same Maven. - `pom.xml`: bump `central-publishing-maven-plugin` from 0.8.0 to 0.11.0. On its own, 0.11.0 does not fix the Maven 3.10 issue.
vharseko
added a commit
to OpenIdentityPlatform/OpenDJ
that referenced
this pull request
Oct 11, 2026
…to 0.11.0 (#1187) Refs OpenIdentityPlatform/commons#325 (workaround only, the issue stays open) ## Problem Since the `ubuntu-24.04` runner image 20261004 replaced the system Maven 3.9.x with 3.10.0, releases to Maven Central fail in validation: ``` Bundle has content that does NOT have a .pom file: <every artifact directory> ``` Under Maven 3.10, `central-publishing-maven-plugin` leaves local-repository files in its staging directory, and they end up in `central-bundle.zip`: - `maven-metadata-local.xml` in every artifact directory - `_remote.repositories` (+ checksums) in every version directory This first hit OpenIdentityPlatform/commons in release run [38121296549](https://github.com/OpenIdentityPlatform/commons/actions/runs/38121296549). The commons issue has the local reproduction and the upstream links. Plugin 0.8.0 and 0.11.0 behave the same. ## Changes Same workaround as OpenIdentityPlatform/commons#324: - `release.yml`: before the release, install Maven 3.9.16 from `archive.apache.org` with a pinned sha512 and put it first on `PATH`. `release:perform` runs its nested build with the same Maven. - `pom.xml`: bump `central-publishing-maven-plugin` from 0.8.0 to 0.11.0. On its own, 0.11.0 does not fix the Maven 3.10 issue.
vharseko
added a commit
to OpenIdentityPlatform/OpenICF
that referenced
this pull request
Oct 11, 2026
…to 0.11.0 (#179) Refs OpenIdentityPlatform/commons#325 (workaround only, the issue stays open) ## Problem Since the `ubuntu-24.04` runner image 20261004 replaced the system Maven 3.9.x with 3.10.0, releases to Maven Central fail in validation: ``` Bundle has content that does NOT have a .pom file: <every artifact directory> ``` Under Maven 3.10, `central-publishing-maven-plugin` leaves local-repository files in its staging directory, and they end up in `central-bundle.zip`: - `maven-metadata-local.xml` in every artifact directory - `_remote.repositories` (+ checksums) in every version directory This first hit OpenIdentityPlatform/commons in release run [38121296549](https://github.com/OpenIdentityPlatform/commons/actions/runs/38121296549). The commons issue has the local reproduction and the upstream links. Plugin 0.8.0 and 0.11.0 behave the same. ## Changes Same workaround as OpenIdentityPlatform/commons#324: - `release.yml`: before the release, install Maven 3.9.16 from `archive.apache.org` with a pinned sha512 and put it first on `PATH`. `release:perform` runs its nested build with the same Maven. - `pom.xml`: bump `central-publishing-maven-plugin` from 0.8.0 to 0.11.0. On its own, 0.11.0 does not fix the Maven 3.10 issue.
vharseko
added a commit
to OpenIdentityPlatform/OpenIG
that referenced
this pull request
Oct 11, 2026
…to 0.11.0 (#185) Refs OpenIdentityPlatform/commons#325 (workaround only, the issue stays open) ## Problem Since the `ubuntu-24.04` runner image 20261004 replaced the system Maven 3.9.x with 3.10.0, releases to Maven Central fail in validation: ``` Bundle has content that does NOT have a .pom file: <every artifact directory> ``` Under Maven 3.10, `central-publishing-maven-plugin` leaves local-repository files in its staging directory, and they end up in `central-bundle.zip`: - `maven-metadata-local.xml` in every artifact directory - `_remote.repositories` (+ checksums) in every version directory This first hit OpenIdentityPlatform/commons in release run [38121296549](https://github.com/OpenIdentityPlatform/commons/actions/runs/38121296549). The commons issue has the local reproduction and the upstream links. Plugin 0.8.0 and 0.11.0 behave the same. ## Changes Same workaround as OpenIdentityPlatform/commons#324: - `release.yml`: before the release, install Maven 3.9.16 from `archive.apache.org` with a pinned sha512 and put it first on `PATH`. `release:perform` runs its nested build with the same Maven. - `pom.xml`: bump `central-publishing-maven-plugin` from 0.8.0 to 0.11.0. On its own, 0.11.0 does not fix the Maven 3.10 issue.
vharseko
added a commit
to OpenIdentityPlatform/OpenIDM
that referenced
this pull request
Oct 12, 2026
…to 0.11.0 (#254) Refs OpenIdentityPlatform/commons#325 (workaround only, the issue stays open) ## Problem Since the `ubuntu-24.04` runner image 20261004 replaced the system Maven 3.9.x with 3.10.0, releases to Maven Central fail in validation: ``` Bundle has content that does NOT have a .pom file: <every artifact directory> ``` Under Maven 3.10, `central-publishing-maven-plugin` leaves local-repository files in its staging directory, and they end up in `central-bundle.zip`: - `maven-metadata-local.xml` in every artifact directory - `_remote.repositories` (+ checksums) in every version directory This first hit OpenIdentityPlatform/commons in release run [38121296549](https://github.com/OpenIdentityPlatform/commons/actions/runs/38121296549). The commons issue has the local reproduction and the upstream links. Plugin 0.8.0 and 0.11.0 behave the same. ## Changes Same workaround as OpenIdentityPlatform/commons#324: - `release.yml`: before the release, install Maven 3.9.16 from `archive.apache.org` with a pinned sha512 and put it first on `PATH`. `release:perform` runs its nested build with the same Maven. - `pom.xml`: bump `central-publishing-maven-plugin` from 0.8.0 to 0.11.0. On its own, 0.11.0 does not fix the Maven 3.10 issue.
vharseko
added a commit
that referenced
this pull request
Nov 6, 2026
Fixes #325 Upgrade `org.sonatype.central:central-publishing-maven-plugin` from 0.11.0 to 0.12.0, the latest release published to Maven Central. Version 0.12.0 removes the Maven 3.10 local-repository metadata, tracking files, and locks before bundling, fixing Central's “Bundle has content that does NOT have a .pom file” rejection. Remove the Maven 3.9.16 installation step introduced by #324 so releases use the runner's Maven again. The fix is documented in the [official 0.12.0 release notes](https://central.sonatype.org/publish/publish-portal-maven/#0120-13-oct-2026) and [upstream PR #3](sonatype-nexus-community/central-publishing-maven-plugin#3). Validation on Maven 3.10.0 / JDK 11: - Reproduced the issue with 0.11.0: the parent POM bundle contains six unwanted repository files. With 0.12.0, it contains only the POM and its four checksums. - Built and tested the four-module `i18n-framework/core` reactor through `deploy`, including sources and Javadoc: 45 tests passed; the bundle contains 50 files and no repository metadata, tracking files, or locks. Used a release-version copy and `-DskipUpload=true`; nothing was uploaded to Central. - Checked workflow YAML, POM XML, and `git diff --check`.
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.
Refs #325 (workaround only, the issue stays open)
Problem
The
Release Mavenrun 38121296549 for 3.2.1 built and tested all modules, then failed incentral-publishing-maven-plugin:0.8.0:publish. Maven Central rejected the deployment:All 103 artifact directories and
org/openidentityplatform/commonswere listed.Root cause
The 3.2.0 release (36534373230) staged exactly the same file list with the same plugin and JDK. The only change is the runner image:
ubuntu-24.0420261004 replaced the system Maven 3.9.x with 3.10.0.Under Maven 3.10, the plugin's staging directory also gets local-repository files, and they end up in
central-bundle.zip:maven-metadata-local.xmlin every artifact directory_remote.repositories(+.md5/.sha*) in every version directoryCentral then sees an artifact directory with content but no
.pom.I reproduced this locally with version
3.2.1,deploy -pl i18n-framework/core -am, and the upload blocked:Changes
release.yml: before the release, install Maven 3.9.16 fromarchive.apache.orgwith a pinned sha512 and put it first onPATH.release:performruns its nested build with the same Maven.pom.xml: bumpcentral-publishing-maven-pluginfrom 0.8.0 to 0.11.0. On its own, 0.11.0 does not fix the Maven 3.10 issue.Not verified:
deploy.yml(snapshot publishing) still uses the runner's Maven 3.10. Snapshots do not go through the bundle.