bitcoindevkit
Migrate OSSRH namespace to the Central Portal for Kotlin/Java artifacts
I got the below email from the maven central team. We need to determine how this will affect our publishing for maven artifacts.
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
Looking at this this morning. Will leave links and info here.
https://central.sonatype.org/faq/what-is-different-between-central-portal-and-legacy-ossrh/
One thing that will need fixing is our automatic deployment using Gradle, which is not currently supported directly by Gradle. There are 3rd party options, but it's a bit of research. But honestly I'm quite pumped about this, because the old stuff and the old plugins were super hard to work with. I expect the long-term solution will be much more robust.
I have managed to publish an artifact using the manual approach this afternoon. It's quite a workflow so the plugin will be welcome once it arrives (or we can pick one of the very popular 3rd party ones, 1000+ stars), but for now at least this should not block our 2.0 release.
I'll just have to be the one building and publishing the jvm and android artifacts.
The bdk-android 2.0.0 library is out. I used this approach (build locally, bundle manually, upload the artifact).
The JVM library will require a bit more work, because I can't cross-compile locally for all our targets. I think the way to do it will be a CI job that outputs the binaries to a directory I can download, and then manually building and uploading.
This is now done. I'm still waiting on an official plugin from Gradle to automate our releases, but for now we do it with a bit of manual work and it's not too hard.