CODEWITHSUNDEEP
androidandroid-studioandroid-gradle-plugin
Valeriy Katkov
Valeriy Katkov

Reputation: 40522

"JCenter is at end of life" android lint warning, what is the replacement?

Android Studio Arctic Fox Canary 8 started to warn that JCenter is at end of life

enter image description here

But I cannot just delete jcenter() declarations since it hosts a lot of android artifacts, it would lead to Could not resolve all artifacts error. What is the right way to solve this warning?

Upvotes: 121

Views: 31420

Answers (5)

NSV.
NSV.

Reputation: 61

Wait. Let JCenter come to end of service. Then, pull out the new repositry. It's fine to ignore warnings totally.

Upvotes: 4

P R
P R

Reputation: 105

Find lines that say jcenter() and add mavenCentral() before each of them (Make sure to add mavenCenteral() in both spots where jcenter() is found.)

Adding Maven Central before JCenter means Maven Central will be used by default, and JCenter will still be used as a fallback.

If you attempt to remove jcenter() completely today from your Android project, you may get the following error.

> Could not resolve all artifacts for configuration ':classpath'.
   > Could not find org.jetbrains.trove4j:trove4j:20160824.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/trove4j/trove4j/20160824/trove4j-20160824.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/trove4j/trove4j/20160824/trove4j-20160824.pom
     Required by:
         project : > com.android.tools.build:gradle:4.1.2 > com.android.tools.build:builder:4.1.2 > com.android.tools:sdk-common:27.1.2

The reason for this error is that the Android Core dependency still requires JCenter.

Android Studio 4.1.2 and AGP (Android Gradle Plugin) still require a version of a dependency (trove4j) that is only on JCenter.

This is solved in AGP 4.2.0, but this is still in beta and requires Android Studio 4.2 beta or newer.

Upvotes: 3

user_MGU
user_MGU

Reputation: 1073

Do not hurry! Nothing needs to be done until the developers of Android Studio make an adequate automatic solution for this situation

Upvotes: 5

Ivan Bila
Ivan Bila

Reputation: 767

I think that to adhere to a non-breaking migration, instead of deleting the jcenter(), you can keep both and only changing the order in the script itself. That way, jcenter() will always be a fallback to mavenCentral() while the developers are in the process of migrating their artifacts.

repositories {
    google()
    mavenCentral()  
    jcenter()       
}

Upvotes: 54

Valeriy Katkov
Valeriy Katkov

Reputation: 40522

There's a documentation section describing the problem: JCenter deprecation and end of service. You can find the link by expanding the inspection description (Ctrl+F1). The documentation states:

JFrog, the company that maintains the JCenter artifact repository used by many Android projects, recently announced the deprecation and upcoming retirement of JCenter. According to the announcement, JCenter will allow downloads of existing artifacts until February 1, 2022.

Developers who publish artifacts on JCenter should start migrating their packages to a new host, such as Maven Central.

In the near future, we will provide additional information about migrating Android projects away from JCenter on this page.

The expanded inspection description (as well as the documentation above) suggests to replace jcenter() by mavenCentral(). Acually JCenter is a superset of Maven Central, but such a replacement won't resolve the problem until all JCenter artifacts your project uses will be moved to Maven Central.

I think the optimal solution would be to wait until the libraries you're using are moved from jcenter() and try to replace it with mavenCentral(). If some artifacts are still missing, take a look at the documentation, may be they are moved into another repository and you should add it to the repositories list as well.

repositories {
    google()

//  jcenter()       // <- removed
    mavenCentral()  // <- added
}

If you're a library author you should migrate to another repo, probably it would be Maven Central. Note that according to the JCenter deprecation announcement new submissions are allowed only until March 31st 2021.

A few related resources:

Upvotes: 136

Related Questions