OSSRH end-of-life on June 30th, 2025

Summary

The OSSRH will reach end-of-life by June 30th, 2025.

What is the expected correct behavior?

We will need to figure out how to do the staging of the Jakarta EE artifacts.

Relevant logs and/or screenshots

https://central.sonatype.org/faq/what-is-different-between-central-portal-and-legacy-ossrh/#process-to-migrate

(Add a link to or paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

Luckily, we should be done with Jakarta EE 11 by then (fingers crossed). The new solution must be running fairly quickly to avoid disruption in the development of Jakarta EE 12.

added team:releng label

added IT-priorityhigh IT-severitymajor service:ossrh labels

We will get in touch with Sonatype support and find out how to do the migration.

assigned to @fgurr

added statewip label

mentioned in issue #5913

mentioned in issue #6116 (closed)

The technology.lyo project would need assistance with this too, please. Our current releng depends on Jenkins (#6115 (closed)). If the releng team would kindly provide a supported path to migrate from OSSRH+Jenkins to the new Portal + GH Actions, we would do our best to adopt.

marked this issue as related to #5913

marked this issue as related to #6084

marked this issue as related to #5935 (closed)

marked this issue as related to #6049 (closed)

marked this issue as related to #6027 (closed)

marked this issue as related to #6130

marked this issue as related to #6048 (closed)

marked this issue as related to #6146 (closed)

marked this issue as related to #6159 (closed)

I've posted an update here: https://www.eclipse.org/lists/cross-project-issues-dev/msg20055.html

@igrimstad please spread the word in the ee4j community to make them aware of the upcoming changes.

marked this issue as related to #6167 (closed)

marked this issue as related to #6168