Skip to content

OSSRH: Migrate Namespace to Maven Central #132

Closed

Description

@Weltraumschaf

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

TODOs

Relates to: secureCodeBox/secureCodeBox#3130

Activity

  1. moved this from Triage to Todo in secureCodeBoxon May 9, 2025
  2. self-assigned this
    on May 9, 2025
  3. moved this from Todo to In Progress in secureCodeBoxon May 26, 2025
  4. Weltraumschaf commented on May 26, 2025

    @Weltraumschaf
    MemberAuthor
  5. Weltraumschaf commented on May 26, 2025

    @Weltraumschaf
    MemberAuthor

    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>
  6. Weltraumschaf commented on May 28, 2025

    @Weltraumschaf
    MemberAuthor
  7. self-assigned this
    on Sep 9, 2025
  8. added 2 commits that reference this issue on Sep 15, 2025
  9. moved this from In Progress to Done in secureCodeBoxon Sep 15, 2025
  10. moved this from Backlog to In Progress in secureCodeBoxon Sep 16, 2025
  11. added a commit that references this issue on Sep 16, 2025
  12. Weltraumschaf commented on Sep 24, 2025

    @Weltraumschaf
    MemberAuthor

    On-/Offboarding doc notes:

  13. added a commit that references this issue on Sep 24, 2025
  14. moved this from In Progress to Done in secureCodeBoxon Sep 24, 2025
  15. Weltraumschaf commented on Sep 24, 2025

    @Weltraumschaf
    MemberAuthor

    @p4trickweiss Thanks for fixing this. I'll do the on-/off-boarding docs update, then its done.

  16. moved this from Backlog to Todo in secureCodeBoxon Sep 24, 2025
  17. Weltraumschaf commented on Sep 25, 2025

    @Weltraumschaf
    MemberAuthor

    I've updated our internal on-/off-boarding doc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions