What Publishers Need to Know About Migrating from JCenter / Bintray to The Central Repository

We know the news about JFrog sunsetting Bintray/JCenter has been unsettling for many. Our goal is to make the migration to The Central Repository as easy as possible – whether you’re just consuming components or if you’re publishing them as well. You can also read more about our commitment to Central in a recent blog post by Sonatype Co-Founder & Maven grandee Brian Fox. 

In this article, we’re talking specifically about what publishers need to know as they migrate. Any migration is going to have its friction, especially with such strict timelines as JCenter’s shutdown schedule. Let’s face it, moving off a platform in less than 6 months is going to be a serious challenge to most organizations. Still, we’d wager it’s easier than you think.

There are a ton of great guides to help you with this if you prefer reading external blogs. Check out the below for some great tips. As these migrations mostly affect Android and Gradle, you can find some great material on those below as well as a comprehensive maven guide

The main avenue for publishing into The Central Repository is via a service known as Sonatype OSSRH (OSS Repository Hosting)- OSSRH uses the Maven repository format and allows you to:

  • deploy development version binaries (snapshots)
  • stage release binaries
  • promote release binaries and sync them to the Central Repository

The difference between publishing to JCenter via Bintray vs OSSRH is most evident in the initial setup for your OSSRH repository, as the process requires some manual one-time steps and one-time review on our side.

The reason for the above is Central is committed to protecting the integrity of projects published to it. As key (Read more…)

*** This is a Security Bloggers Network syndicated blog from Sonatype Blog authored by Ilkka Turunen. Read the original post at: https://blog.sonatype.com/what-publishers-need-to-know-about-migrating-from-jcenter-/-bintray-to-the-central-repository