Will there be an advice from JetBrains about this JCenter si

Question

Will there be an advice from JetBrains about this JCenter situation Since it will seriously impact the Kotlin Ecosystem Will there maybe be a Jetbrains solution Since I would trust that more than another random company which is less invested in the Kotlin ecosystem

Vampire · Answer

What s wrong with using Maven Central I always published things to Maven Central because that is what in most builds is present and for Maven consumers even is available by default The only hard part is the initial getting registered but after that it just works

Timo Gruen · Answer

It s an issue for the whole Java Ecosystem Currently I would rather say that most dependencies are present in maven central only very limited are present in jCenter only hopefully all of those are getting migrated

Kirill Grouchnikov · Answer

It s all good until Maven Central disappears

Vampire · Answer

Unlikely at least as long as Maven exists it s the canonical repository I would really wonder if it vanishes smile

Kirill Grouchnikov · Answer

It eventually will Nothing is forever

napperley · Answer

Isn t Maven Central separate from the Maven build system

Kirill Grouchnikov · Answer

I m just saying that somebody is paying for all that bandwidth disk space security procedures etc At some point that somebody will not be there

napperley · Answer

One wonders if JetBrains see a valuable opportunity to fill in the enormous gap by providing a similar service with the difference being that it is geared toward Kotlin libraries

napperley · Answer

It is true that the funding for the service to keep the lights on would need to come from somewhere Should JetBrains provide a service geared towards Kotlin libraries that would easily be covered with paid plans for commercial software libraries A special free plan would be provided for open source software libraries with certain limitations the devil is in the details

napperley · Answer

Admittedly I have some open source Kotlin libraries that depend on Bintray for publishing unstable versions and was planning to use JCenter for publishing production versions but with this news that has gone out the window white frowning face

napperley · Answer

What advice would the Kotlin team give about publishing an open source Kotlin library Is there a credible alternative to Maven Central that can be used

Kirill Grouchnikov · Answer

Maven Central is still there Setting it up is a bit of a hassle though

napperley · Answer

I have heard that it is a enormous hassle for Multiplatform Kotlin libraries

napperley · Answer

What is to stop Maven Central from disappearing into the sunset

Kirill Grouchnikov · Answer

You can ask that of any other existing and future solution

napperley · Answer

This would be no different if PyPy Npm or any other similar service were to permanently go off the air

Kirill Grouchnikov · Answer

We re kinda going in circles Maven Central is already there as a free solution I guess you re asking for another solution that doesn t exist yet on an extremely tight deadline with no clear long term sustainability plan

Michal Klimczak · Answer

How is maven central more of a hassle fkr multiplatform than any other library I understand the initial hassle of setting up the repository account but otherwise it s just another repo it should work regardless of whether your maven repo contains kmm or regular kotlin or java or whatever right

louiscad · Answer

mavenCentral has a bunch of free public mirrors though and jcenter was partly one of them BTW Google hosts some mavenCentral mirrors in several GCP regions for instance

napperley · Answer

With the Google thing you are relying on yet another service additional point of failure

Javier · Answer

< napperley> in fact I moved from bintray to mavenCentral because it is easier to update multiplatform libraries

louiscad · Answer

< Javier> What is easier exactly

Javier · Answer

I uploaded a lib with two targets to Jcenter later I added a new target but it wasn t appearing I asked the support team and they said me something about metadata I don t remember right now with MavenCentral I have to do nothing if I add a new target it will be there btw I had this problem long time ago Maybe it had changed