On June 1, JBoss Nexus will move to Nexus 3. This introduces two key changes:

1) The old 'staging suite' is gone. Deploying using the default maven-deploy-plugin will now directly publish artifacts to the main repo as each module in a build processes. This is somewhat risky for multi-module builds, as failure in later modules leaves a partly published release. If the release can be completed using 'mvn -rf' perhaps all is well, but if not, or if there is some other problem with the release it can't be withdrawn.

For repos that produce feature packs, there is also the possibility that the feature pack will be published, and thus be consumable by users of Galleon-based tooling, while parts of the release failed to deploy.

To avoid this, we should use a staging repo and use the nxrm3-maven-plugin to deploy, using the staging-deploy to initially deploy and then the staging-move goal when all is ready.

https://github.com/sonatype/nxrm3-maven-plugin?tab=readme-ov-file#staging

2) When artifacts are deployed they will be pushed to maven central, instead of the old style pull that happened. Because of or perhaps just related to this, enforcement of maven central requirements that we've long not met will now happen. In particular we need to sign our artifacts.

https://central.sonatype.org/publish/requirements/

This issue is a kind of epic to track various changes needed to be ready for this.