Repository navigation
Conversation
vharseko
added
bug
dependencies
This was referenced Nov 6, 2026
Merged
Merged
Merged
Merged
maximthomas
self-requested a review
November 6, 2026 12:49
maximthomas
approved these changes
Nov 6, 2026
vharseko
added a commit
to OpenIdentityPlatform/OpenDJ
that referenced
this pull request
Nov 6, 2026
) Fixes OpenIdentityPlatform/commons#325. Follows #1187 and OpenIdentityPlatform/commons#388. Upgrade `org.sonatype.central:central-publishing-maven-plugin` from 0.11.0 to 0.12.0 and remove the Maven 3.9.16 installation step introduced by #1187. Releases use the runner's Maven again. Version 0.12.0 removes the local-repository metadata, tracking files, and locks that Maven 3.10 writes into the staging directory, preventing Central's “Bundle has content that does NOT have a .pom file” rejection. See the [official release notes](https://central.sonatype.org/publish/publish-portal-maven/#0120-13-oct-2026) and [upstream fix](sonatype-nexus-community/central-publishing-maven-plugin#3). Validation: - POM XML and workflow YAML parse; `git diff --check` passes. - Parent POM staging with Maven 3.10.0 / JDK 11, using a temporary release-version copy, dummy credentials, and `deploy -N -DskipUpload=true` completed successfully. The bundle contains exactly the parent POM and its four checksums, with no Maven metadata, tracking files, or locks. Nothing was uploaded to Central. The full reactor and actual release workflow were not run.
vharseko
added a commit
to OpenIdentityPlatform/OpenAM
that referenced
this pull request
Nov 6, 2026
) Fixes OpenIdentityPlatform/commons#325. Upgrade `org.sonatype.central:central-publishing-maven-plugin` from 0.11.0 to 0.12.0 and remove the Maven 3.9.16 installation step introduced by #1165. Releases can use the runner's Maven again because 0.12.0 removes Maven 3.10 metadata, tracking files, and locks before bundling. 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). This applies the same update as [commons #388](OpenIdentityPlatform/commons#388). Validation on Maven 3.10.0 / JDK 11: - Reproduced the old parent POM bundle's six unwanted repository files with plugin 0.11.0 and upload directed to a closed loopback port. With 0.12.0 and `-DskipUpload=true`, `deploy -N` succeeds and the bundle contains only the POM and its four checksums. Used a temporary release-version copy, dummy credentials, and skipped GPG signing. - POM XML and release workflow YAML parse, and `git diff --check` passes. The full reactor and the GitHub release workflow were not run.
vharseko
added a commit
to OpenIdentityPlatform/OpenIG
that referenced
this pull request
Nov 6, 2026
Fixes OpenIdentityPlatform/commons#325. Upgrade `org.sonatype.central:central-publishing-maven-plugin` from 0.11.0 to 0.12.0, the latest release published to Maven Central. It removes 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 setup introduced by #185, following OpenIdentityPlatform/commons#388. 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: - Maven 3.10.0 / JDK 11: parent-only `deploy -N` using a temporary release-version copy and `-DskipUpload=true` passed. The bundle contains 10 artifact/checksum files and no repository metadata, tracking files, or locks. Nothing was published to Central. - Parsed the POM XML and workflow YAML, checked that the Maven pin is the only workflow change, and ran `git diff --check`. - Full application test suites were not run for these build-configuration changes.
vharseko
added a commit
to OpenIdentityPlatform/OpenICF
that referenced
this pull request
Nov 6, 2026
Fixes OpenIdentityPlatform/commons#325. Follows #179 and OpenIdentityPlatform/commons#388. Upgrade `org.sonatype.central:central-publishing-maven-plugin` from 0.11.0 to 0.12.0. 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 #179 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: - Ran the root POM through `deploy -N` in a temporary release-version copy with dummy credentials and `-DskipUpload=true`. The 0.12.0 build succeeded and explicitly skipped the upload; its bundle contains only the POM and four checksums, with no repository metadata, tracking files, or locks. - Checked workflow YAML, POM XML, and `git diff --check`. The full reactor and a live Maven Central deployment were not run.
vharseko
added a commit
to OpenIdentityPlatform/OpenIDM
that referenced
this pull request
Nov 6, 2026
Fixes OpenIdentityPlatform/commons#325. Upgrade `org.sonatype.central:central-publishing-maven-plugin` from 0.11.0 to 0.12.0, the latest release published to Maven Central. It removes 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 setup introduced by #254, following OpenIdentityPlatform/commons#388. 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: - Maven 3.10.0 / JDK 17: parent-only `deploy -N` using a temporary release-version copy and `-DskipUpload=true` passed. The bundle contains 5 artifact/checksum files and no repository metadata, tracking files, or locks. Nothing was published to Central. - Parsed the POM XML and workflow YAML, checked that the Maven pin is the only workflow change, and ran `git diff --check`. - Full application test suites were not run for these build-configuration changes.
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.
Fixes #325
Upgrade
org.sonatype.central:central-publishing-maven-pluginfrom 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 and upstream PR #3.
Validation on Maven 3.10.0 / JDK 11:
i18n-framework/corereactor throughdeploy, 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.git diff --check.