Skip to content

Drop nexus-staging-maven-plugin and GPG signing from the release profile - #691

Merged
gastaldi merged 1 commit into
mainfrom
maven310
Oct 15, 2026
Merged

gastaldi merged 1 commit into
mainfrom
maven310

Conversation

@gastaldi

@gastaldi gastaldi commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Removes nexus-staging-maven-plugin from both pluginManagement and the release profile, and drops the maven-gpg-plugin sign-artifacts execution from the release profile.

The release profile is now auto-activated by the presence of the performRelease property, so maven-release-plugin picks it up without an explicit -Prelease.

Also included:

  • The version.nexus.staging.plugin property is dropped as well, per review feedback — downstream poms that still reference it can fix it when they bump the parent. (It would be broken anyway: the plugin itself has changed, see https://help.sonatype.com/en/nexus-repository-maven-plugin.html)
  • distributionManagement is repointed off the legacy s01.oss.sonatype.org staging/snapshot endpoints and onto Central Sonatype, under a single smallrye-publish server id.

The version.surefire revert from 3.6.0 back to 3.5.6 (SUREFIRE-3460) was split out into #692 to make it easier to track, so it is no longer part of this PR.

@gastaldi
gastaldi marked this pull request as draft October 13, 2026 13:24
@dmlloyd

dmlloyd commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

Are there really downstream projects referencing version.nexus.staging.plugin or is it just over-cautious AI? I think you could probably just drop it. It's OK if a version bump breaks a downstream build; they can just fix the POM at the same time they update the parent.

@gastaldi

Copy link
Copy Markdown
Contributor Author

@dmlloyd if they reference it, it would no longer work, since the plugin changed: https://help.sonatype.com/en/nexus-repository-maven-plugin.html

Comment thread pom.xml Outdated
@gastaldi
gastaldi marked this pull request as ready for review October 13, 2026 15:39
Remove the nexus-staging-maven-plugin from both pluginManagement and the
release profile, and drop the maven-gpg-plugin sign-artifacts execution.

Also auto-activate the release profile when the performRelease property is
set, so it is picked up by maven-release-plugin without passing -Prelease.

@dmlloyd dmlloyd left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good; is this all ready?

@gastaldi

Copy link
Copy Markdown
Contributor Author

Yes, it should be good now

@gastaldi
gastaldi merged commit 9c5f83f into main Oct 15, 2026
1 check passed
@github-actions github-actions Bot added this to the 53 milestone Oct 15, 2026
@gastaldi
gastaldi deleted the maven310 branch October 15, 2026 16:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants