Skip to content

OSSRH: Migrate Namespace to Maven Central #132

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Weltraumschaf opened this issue May 9, 2025 · 4 comments
Open

OSSRH: Migrate Namespace to Maven Central #132

Weltraumschaf opened this issue May 9, 2025 · 4 comments
Assignees

Comments

@Weltraumschaf
Copy link
Member

Today got this reminder per Mail:

NOTE: If you have already migrated your namespace(s) to Maven Central this email does not apply to you and thank you for your initiative.

Greetings OSSRH Publisher,

As you may have heard, OSSRH is reaching end of life on June 30, 2025. OSSRH users need to migrate their namespaces to the Central Portal as soon as possible.

Instructions for self migration are located here: https://central.sonatype.org/faq/what-is-different-between-central-portal-and-legacy-ossrh/#self-service-migration

To make the transition smoother we will be automatically migrating publishers that have not used oss.sonatype.org or s01.sonatype.org to publish artifacts in some time starting with the oldest and working our way forward. To avoid disruption to your publishing processes we strongly encourage migrating before the June 30, 2025 deadline.

Thank you for your assistance,

The Central Team

@Weltraumschaf Weltraumschaf moved this from Triage to Todo in secureCodeBox v4 May 9, 2025
@Weltraumschaf Weltraumschaf self-assigned this May 9, 2025
@Weltraumschaf Weltraumschaf moved this from Todo to In Progress in secureCodeBox v4 May 26, 2025
@Weltraumschaf
Copy link
Member Author

@Weltraumschaf
Copy link
Member Author

From docs:

How do I know if I am on Legacy OSSRH?

If you use https://oss.sonatype.org or https://s01.sonatype.org to publish, you are publishing via the Legacy OSSRH service. If you are publishing via a build tool integration, this might be configured as a default, so check the plugin's documentation to be sure, if you didn't manually specify a URL.

We're affected:

docs/release.md
31:- Upload the resulting artifacts to [Sonatype Nexus](https://oss.sonatype.org/) and stage them.

pom.xml
198:      <url>https://oss.sonatype.org/content/repositories/snapshots</url>
202:      <url>https://oss.sonatype.org/service/local/staging/deploy/maven2/</url>
350:            <nexusUrl>https://oss.sonatype.org/</nexusUrl>

@Weltraumschaf
Copy link
Member Author

Weltraumschaf commented May 26, 2025

TODOs

@Weltraumschaf
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

1 participant