Migrating to central portal from OSSRH, due to OSSRH shutdown in summer'25

[wadoon]

Related Issue

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

Intended Change

Make gradle publish work again.

Found Bugs

key.core.calculus used a fixed version number. Version should not be overridden in modules, it is inherited by the top module.

Plan

• Should relatively works as before. Real test on next release. Snapshots updated. See Prepare for key-2.12.4 wadoon/key-citool#73

• BACKUP PLAN: Currently, Gradle can not deploy to the new central portal. The legacy support has not worked. The current only way to deploy is:

  gradle --parallel publishMavenJavaPublicationToLocalRepoRepository
  cd localRepo && zip -9 -r ../localRepo.zip . 

  1. It deploys the maven structure to the folder localRepo/
  2. It zips the structure in a correct way.
  3. SNAPSHOTs are not supported, argh...

  The zip file can be then uploaded to the central portal.

Type of pull request

• Preventing rotting

Ensuring quality

• I upload it to the central portal and it gets validated. Final test only possible with a release.

[wadoon]

@unp1 It should work now, but for the final test, we need a release.