Migrate from OSSRH to Maven Central publishing

[kriegaex]

@aclement, maybe you also received an e-mail like this lately:

References:

• https://central.sonatype.org/faq/what-is-different-between-central-portal-and-legacy-ossrh/#self-service-migration
• https://central.sonatype.org/publish/publish-portal-maven/

As you can see on the latter page, publishing artifacts from Maven seems to need a different type of plugin. The docs also mention that the tokens for publishing are different between OSSRH (legacy) and Maven Central (new). Therefore, I do not want to click the following button without your consent, even though org.aspectj seems to be available for self-service migration:

With me being on hiatus, still waiting for sponsorship, and you the only active maintainer at present, you are the one who should decide when to migrate and adjust the Maven build process accordingly.

[kriegaex]

An additional thing to consider: Central Publishing Maven Plugin (CP) can, like the currently used Nexus Staging Maven Plugin (NS), deploy the artifacts and wait for verification. Optionally, it can also auto-publish the staging repository, waiting for the result with a timeout. This could take anywhere from 5 to 30 minutes, hence the long default timeout of 30 minutes. I am not sure that it is such a nice thing to stall the build for so long, but it would certainly be an option.

Currently, with NS the AspectJ release instructions say to deploy first and later to call the plugin again to publish the open staging repository (goals nexus-staging:rc-list, mvn nexus-staging:rc-release). It seems as if CP is unable to do that, as it has only a single goal, not a whole bunch of them like NS. My assumption is that every call of this goal will create a new staging repository. Therefore, we have 3 options:

1. Use a single build step with auto-publish and a potentially long waiting time for completion.
2. Deploy without publishing, then manually publish from https://central.sonatype.com/publishing.
3. Deploy without publishing, then publish via Publish Portal API (REST), e.g. using curl or similar.

None of these variants are perfect, because 1 is long-running, 2 and 3 are not mavenised. Maybe, a future CP plugin version has more goals. However, option 1 might be good for future releases being done from a CI pipeline such as GitHub Actions or Jenkins.

[aclement]

I saw the same email and knew about it before hand, haven't decided when/if I can do anything yet.