Migrate from deprecated nexus-staging-maven-plugin to central-publishing-maven-plugin

[Copilot]

The nexus-staging-maven-plugin is deprecated. Maven Central now uses the central-publishing-maven-plugin for artifact publication.

Changes

Plugin replacement:

• org.sonatype.plugins:nexus-staging-maven-plugin:1.6.6 → org.sonatype.central:central-publishing-maven-plugin:0.6.0

Configuration parameters:

• serverId → publishingServerId
• nexusUrl → (removed)
• autoReleaseAfterClose → autoPublish

Removed distributionManagement override:

• The distributionManagement section in the release profile has been removed to allow the central-publishing-maven-plugin to handle the deployment flow through its own mechanism, rather than using Maven's standard deploy process.

All changes are scoped to the release profile. The GPG signing configuration remains unchanged.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

Migrates the release profile’s Maven Central publishing setup from the deprecated nexus-staging-maven-plugin to central-publishing-maven-plugin, updating the target endpoint and configuration keys.

Changes:

• Replaced nexus-staging-maven-plugin with central-publishing-maven-plugin in the release profile.
• Updated distributionManagement repository id/url to the new “central” endpoint.
• Updated plugin configuration (serverId → publishingServerId, autoReleaseAfterClose → autoPublish) and removed nexusUrl.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The <distributionManagement><repository><url> is used by Maven’s deploy mechanism as a Maven repository base URL. https://central.sonatype.com/api/v1/publisher is a REST API endpoint (not a standard Maven repository layout), so mvn deploy in this profile is likely to fail when it attempts artifact uploads. Consider either (a) not overriding distributionManagement here and letting the central publishing plugin handle the upload/publish flow, or (b) configuring the build so the standard deploy step is skipped and publishing is performed only via the central publishing plugin’s goals (with distributionManagement not pointing at the API endpoint).

[garricko]

@copilot apply changes based on this feedback by not overriding distributionManagement

[Copilot]

Removed the distributionManagement override from the release profile. The central-publishing-maven-plugin now handles the deployment flow through its own mechanism. (27ad16f)

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• repository.sonatype.org
  • Triggering command: /usr/lib/jvm/temurin-17-jdk-amd64/bin/java /usr/lib/jvm/temurin-17-jdk-amd64/bin/java --enable-native-access=ALL-UNNAMED -classpath /usr/share/apache-maven-3.9.12/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/usr/share/apache-maven-3.9.12/bin/m2.conf -Dmaven.home=/usr/share/apache-maven-3.9.12 -Dlibrary.jansi.path=/usr/share/apache-maven-3.9.12/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/vertx-parent/vertx-parent org.codehaus.plexus.classworlds.launcher.Launcher help:effective-pom -Prelease (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)