Migration from JCenter

Question

Migration from JCenter

jakoss opened this issue 3 years ago · 16 comments

In may this library won't be available from JCenter: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

Please migrate this library to some other repository

Answer 1 · 2021-02-08T18:07:44.000Z

@jakoss Thanks for the reminder. Will do that soon.

Answer 2 · 2021-02-25T08:22:00.000Z

@ncapdevi Any updates on this? Maybe you need help

Answer 3 · 2021-05-06T17:46:30.000Z

Any updates?

Answer 4 · 2021-05-11T07:54:22.000Z

Hi @ncapdevi

I understand migration from jcenter() to mavenCentral() is time taking task and you may not have time for it.
But at least release the .aar file so we can put in project and use it till you not migrate the binary to some other source.

Answer 5 · 2021-05-11T07:56:37.000Z

@ncapdevi Any updates on this one?

Answer 6 · 2021-05-18T10:15:27.000Z

For those having issues with JCenter() here's my temporary solution, replace version if needed

implementation 'com.github.ncapdevi:FragNav:3.2.0'

Answer 7 · 2021-05-18T11:40:04.000Z

@jtorrestobena interesting, is github hosting gradle package automatically for repository?

Answer 8 · 2021-05-18T12:03:41.000Z

Sorry forgot to mention you need jitpack for this:

See here: https://jitpack.io

Answer 9 · 2021-05-24T14:17:04.000Z

@jtorrestobena that is a good idea 👍 Just forked the library and gonna use it on my own git based repo until the library is moved from jcenter

Answer 10 · 2021-06-06T11:36:59.000Z

@jakoss @ncapdevi With all due respect, I think that's kind of easy.
I published my repo by following this guide:
https://medium.com/@ome450901/publish-an-android-library-by-jitpack-a0342684cbd0
I'm sorry if I was wrong.

Answer 11 · 2021-06-06T12:09:37.000Z

@jakoss @ncapdevi With all due respect, I think that's kind of easy.
I published my repo by following this guide:
https://medium.com/@ome450901/publish-an-android-library-by-jitpack-a0342684cbd0
I'm sorry if I was wrong.

Not sure why are addressing this to me, but difficulty isn't really an issue. It's main contributor time. But it's not that important now, since jfrog announced that repositories will be hosted as read only indefinitely.

Answer 12 · 2021-06-06T12:14:59.000Z

@jakoss Thank you!

Answer 13 · 2022-04-05T02:42:30.000Z

But it's not that important now

it's still important. Jcenter is unreliable, it had multiple big outages recently. Many projects do not allow jcenter() repository and jcenter dependencies.
In our case we re-published lib to our own private repo to get rid of jcenter

Also suggested publishing to jitpack is also not an option for many projects because of it not-secure nature and slow performance.

The library should be published to maven central

Answer 14 · 2022-04-05T11:21:58.000Z

Hi @gildor, I would recommend you to fork the library and use it from your own repo, something like this,

implementation 'com.github._yourgithubname_:FragNav:3.2.0'

Answer 15 · 2022-04-06T02:23:12.000Z

This is what we are already doing, as I said in my previous message

Answer 16 · 2022-04-06T02:31:55.000Z

For anyone who wants to re-publish this library to your own repository, you can refer to this PR which includes changes to allow propagate start/pause lifecycle events on show/hide of fragment, but also on the same PR we updated publishing config to be compatible with recent Gradle and Android Gradle Plugin.
To publish to own repo, just change version/group in build.gradle and set gradle properties:
publishRepoUrl
publishRepoUsername
publishRepoPassword

Like:

./gradlew publish -PpublishRepoUrl=URL -PpublishRepoUsername=USERNAME -PpublishRepoPassword=PASSWORD