Migrate eclipse-pass from OSSRH to Central Portal

Summary

We would like to migrate the Java projects in https://github.com/eclipse-pass from OSSRH to Central Portal for releases. We are doing this because Sonatype is going to retire OSSRH.

The following repos are going to be updated:

• https://github.com/eclipse-pass/main
• https://github.com/eclipse-pass/pass-core
• https://github.com/eclipse-pass/pass-support

Based on the docs on Sonatype, we believe our project would qualify for the Self-Service migration option: https://central.sonatype.org/faq/what-is-different-between-central-portal-and-legacy-ossrh/#self-service-migration

We should only have two namespaces (org.eclipse.pass and org.eclipse.pass.deposit). Not sure about the number of Publishers though. We believe that someone at Eclipse Foundation (EF) manages the credentials used for logging into Sonatype, so this migration step would need to be done by someone in EF.

From reading the docs, here is what we are planning for this change:

• EF executes the self-migration step as documented above.
• EF gets user token credentials for central portal https://central.sonatype.org/publish/publish-portal-maven/#credentials
• EF updates the org secrets
• We update the relevant poms to use the central-publishing-maven-plugin maven plugin with org secrets

Please let us know if there is something else we need to do.

Steps to reproduce

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact