Re: [cross-project-issues-dev] OSSRH Service: EOL June 30th, 2025

[Frederic Gurr <frederic.gurr@xxxxxxxxxxxxxxxxxxxxxx>]

Hi,

Since, several projects received reminder emails about the upcoming EOL 
of OSSRH and have opened HelpDesk tickets, we would like to give a brief 
update.

Since there is not much time left before the end of June, we have asked 
Sonatype for an extension, but have not heard back from them.

We've already started to migrate a few projects from OSSRH to the 
Sonatype Central Portal in the meantime.

Eclipse projects do not have to do the migration themselves. They can 
either actively request a migration in a HelpDesk ticket, or wait until 
we will create tickets over the coming weeks and set a date (releases, 
etc will be considered).

In general, there are two kinds of migration processes, depending on the 
setup of the namespaces / group IDs. In most cases, it's a 
straightforward, mostly automated migration that only requires a few 
clicks. In some cases, the migration has to be coordinated with Sonatype 
support via email which can take some time.

To reduce friction, please familiarize yourself with the required 
changes in your build and deployment processes and workflows:
* Maven => https://central.sonatype.org/publish/publish-portal-maven/
* Gradle => https://central.sonatype.org/publish/publish-portal-gradle/

In addition, please note that it's not possible to publish to the same 
namespace via OSSRH and the Central Portal at the same time. Once the 
migration is done, there is no standard way of going back.

Please let us know if you have any questions or concerns.

Regards,

Fred

On 22.04.25 15:52, Sebastien Heurtematte via cross-project-issues-dev wrote:
> Hi all,
>
> For those of you who deploy artifacts to Maven Central, you may have 
> noticed the following message recently posted on oss.sonatype.org 
> <https://oss.sonatype.org>:
>
> "The OSSRH service will reach end-of-life on June 30th, 2025. Learn more 
> about how to transfer to the Central Publishing Portal here."
>
> We would like to inform you that we are currently in contact with 
> Sonatype support to better understand the implications of the announced 
> OSSRH sunsetting and to explore potential next steps or alternatives for 
> Eclipse projects that rely on this service.
>
> We will share updates as soon as more concrete information becomes 
> available.
>
> Best regards,
>
> *Sébastien Heurtematte*
> *Release Engineer| Eclipse Foundation*
> eclipse.org <https://www.eclipse.org/>| X 
> <https://twitter.com/EclipseFdn>| LinkedIn 
> <https://www.linkedin.com/company/eclipse-foundation/>| YouTube 
> <https://www.youtube.com/user/EclipseFdn>| Instagram 
> <https://www.instagram.com/eclipsefoundation/>| Bluesky 
> <https://bsky.app/profile/eclipsefdn.bsky.social>| Mastodon 
> <https://mastodon.social/@EclipseFdn>
>
> Eclipse Foundation <http://www.eclipse.org/>: The Community for Open 
> Collaboration and Innovation
>
>
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
Frederic Gurr
Team Lead - Release Engineering | Eclipse Foundation Europe GmbH

Berliner Allee 47, D-64295 Darmstadt
Handelsregister: Darmstadt HRB 92821
Managing Directors: Gaël Blondelle, Mike Milinkovich, Michael Plagge