Shulou(Shulou.com)06/03 Report--

This article mainly shows you "what are the events in which JCenter service is about to be stopped". The content is simple and clear. I hope it can help you solve your doubts. Let me lead you to study and learn this article "what are the events in which JCenter service is about to be stopped".

Many friends may already know about this, and JCenter is about to be abandoned on Android.

Such an important event is also quite unexpected to me. I thought it was Google who wanted to mess with something else, because Google likes to waste things very much. As it turns out, Google is also a victim this time.

JFrog (the operator of JCenter) announced the major decision on its website on February 3 this year, and a number of software package management and distribution services, including Bintray and JCenter, will be suspended. The link to the original text is as follows:

Https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

JFrog's statement is extremely lethal. Why do you say so? Because it's going to affect all Android developers, yeah, you heard right, it's all.

As long as you are an Android developer, you must have used the services provided by JFrog, and even if you have never heard of the name JFrog, you must have unwittingly used JFrog services.

When we create a new Android project in Android Studio, you can always find a configuration like this in the build.gradle file:

Repositories {google () jcenter ()}

This configuration means to specify from which repositories the current project project can pull dependent libraries for use by the current project.

Where google () refers to Google's own repository, such as many of the first-party libraries we use, such as RecyclerView, Jetpack Components, and so on, are pulled from here.

Jcenter () refers to the JCenter repository provided by JFrog, where almost all third-party open source projects on Android choose to publish libraries here, such as OkHttp, Retrofit, RxJava and other third-party libraries that you integrate in the project.

The third-party library of Android is large, far more than the first-party library of Google. It can be said that any Android project will rely on many third-party open source projects. That's why I say that JFrog's statement is extremely lethal.

Next, let me tell you in detail what the impact of JCenter's suspension of service will be, and the time at which these effects will take effect.

There is no doubt that the discontinuation of JCenter will affect two groups of people: developers and users of open source libraries.

Developers of open source libraries may be the biggest headache for some time to come, because by the time this article is published, you will no longer be able to submit any library updates to JCenter.

According to the time node given by JFrog, JCenter will not accept any new submissions after March 31, 2021.

Coincidentally, I have a new version of open source library (PermissionX) to be released recently. Two days ago, I submitted a new version to JCenter as usual, only to find that I failed to submit it. Then I went to the JFrog official website to find this time node, it is really a pity that the new version can not be released for the time being.

If you are an open source user, you don't have to worry about it for a short time, as JCenter will continue to provide services until February 1, 2022. Until then, you can still pull open source libraries from Android Studio that were submitted to JCenter before March 31, 2021.

That's about all the important things and time nodes in the JFrog announcement, but for the vast majority of Android developers, what should we do now?

I don't think there is much that can be done right now, because there is still one very core player who has not stated his position in the whole incident, and that is Google.

As I just said, Google is also a victim of this incident. Originally, when Android Studio created the project, it integrated JCenter repository by default. I thought Google had established a strategic partnership with JFrog. Unexpectedly, it was announced by JFrog to stop service, which directly affected the ecology of the whole Android open source database.

This happened quite suddenly, and JFrog announced on February 3 that it would no longer accept any new library submissions on March 31. Feeling that Google didn't have enough time to deal with this, it only posted a simple statement on the official website of Android developers:

It probably means that JCenter is going to be out of service and it is recommended that you switch to Maven Central,Google and release the migration plan in the near future.

In fact, I remember that before JCenter, the default third-party warehouse of Android was Maven Central, but now it seems to mean to change it back.

I was wondering if Google would have any plans to build its own repository for third-party open source projects so that it wouldn't have to worry about being suddenly shut down. So I checked with Google and got the answer that Google did not have such a plan, so it seems that there is a good chance that Maven Central will be used.

If you want to publish your open source library to Maven Central now, you can refer to this document to do so:

Https://maven.apache.org/repository/index.html

I have found that some libraries are so responsive that they have now released new versions to Maven Central, such as Glide.

As you can see, in repositories, Glide has replaced jcenter () with mavenCentral ().

However, it is difficult to form a standard by adding repositories manually, so it still needs to be driven by Google. It is believed that before long, when Android Studio creates a new project, the default repository will be changed from jcenter () to mavenCentral ().

However, at present, we can only release a new version of the library to Maven Central, while the old version remains on JCenter. These old versions will be completely inaccessible on February 1 next year, so we still need Google to give a migration plan as soon as possible, so that third-party open source libraries can seamlessly switch from JCenter to Maven Central.

The migration plan will be updated at the following URL, and of course I will write an article to explain it at that time.

These are all the contents of the article "what are the events in which JCenter is about to be discontinued?" Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.