Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wasp-dev] OSSRH Service: Migration Plan (EOL June 30th, 2025)

Hi,

I'm adding the WASP dev mailing list. Would we be okay with being included in the first round of migrations? I'm not aware of any active development, looking at the commit history and mailing list for the project. If no objections are raised, I'd say it would be ok to be included in the first round of migrations.

Let me know if anything else is needed.

Thanks,

Paul Nicolucci

Dear project lead,

We are reaching out to you directly as a project lead of the project: ee4j.wasp.
Your project has been identified as being impacted by the OSSRH service end-of-life, and we want to ensure you are fully informed about the migration plan proposed by the Eclipse Foundation.

Reminder: OSSRH Service End Of Life: June 30th, 2025

Please find below the Migration Timeline:

As the migration date approaches and we have not received confirmation from Sonatype regarding a possible postponement, our focus is now to carry out the migration as efficiently and reliably as possible.

To achieve this, we are proposing a multi-step migration plan adapted to each project's needs, with the following key milestones:

* Now -> June 6: Feedback window - projects may opt out of the June 9 migration and be part of the second phase on June 24 Comment on the migration ticket with a +1 from PL: OSSRH end-of-life on June 30th, 2025(https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5854)
* June 9: First migration batch - all projects (except those that choose to opt out) will be moved to central.sonatype.org
* June 24: Final migration batch - for all remaining projects
* July 1-4: Cleanup - OSSRH secrets removed, legacy accounts deactivated, and obsolete configs cleaned up

If your project needs to delay migration to June 24, please comment in the GitLab ticket above no later than May 30: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5854

If you have any concerns, please either open a new Helpdesk ticket or comment in the top level migration ticket: OSSRH end-of-life on June 30th, 2025

IMPORTANT: Once the migration is complete, you will need to update your project configuration (e.g., change oss.sonatype.org to central.sonatype.org, update credentials in settings.xml, or adjust GitHub Action workflows).
We will provide all the necessary documentation to help you succeed in the migration process as smoothly as possible.


Thank you again for your support and collaboration.


Best regards,

Sebastien Heurtematte
Release Engineer | Eclipse Foundation

Back to the top