Skip to main content
All CollectionsKnowledge BaseHow To
Migrating from JCenter to Maven Central CDN
Migrating from JCenter to Maven Central CDN
Updated over a week ago

JFrog Announcements

  • Initial Announcement 2/3/2021: To streamline the productivity of the JFrog Platform we will be sunsetting Bintray, GoCenter, and ChartCenter services on May 1st, 2021. Bintray helped JFrog support the Java community as the host of the JCenter repository for Java OSS libraries, packages and components.

  • UPDATE 4/27/2021: We listened to the community and will keep JCenter as a read-only repository indefinitely. Our customers and the community can continue to rely on JCenter as a reliable mirror for Java packages.

  • UPDATE 2/28/2021: To better support the community in this migration, JFrog has extended the JCenter new package versions submission deadline through March 31st 2021.

How to migrate from JCenter

Because the builds that use JCenter will be able to resolve dependencies until February 1, 2022 without changes. After that date, there are no guarantees that you will be able to build your software if you continue to use JCenter.

How to migrate from JCenter to Maven Central CDN

  • Remove JCenter from your build.gradle and replace it with Maven Central CDN url

buildscript {
repositories {
//jcenter()
mavenCentral()
maven {
url "https://repo1.maven.org/"
} google()
}
}

allprojects{
repositories {
//jcenter()
mavenCentral()
maven {
url "https://repo1.maven.org/"
} google()
}
}

Verify your changes

  • Run your Bitrise build with the new code changes to confirm everything works as expected.

Maven Central vs Maven Central CDN Uptime

Although JCenter is still available, it is unreliable and Maven Central CDN is a far better choice with 100% uptime. Maven Central without CDN can be down from time to time.

Maven Central - 99.98% Uptime

Maven Central CDN - 100% Uptime

Did this answer your question?