Migration from JCenter about fragnav HOT 16 OPEN

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

from fragnav.

Sorry forgot to mention you need jitpack for this:

See here: https://jitpack.io

from fragnav.

@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.

from fragnav.

@ncapdevi Any updates on this? Maybe you need help

from fragnav.

Any updates?

from fragnav.

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.

from fragnav.

@ncapdevi Any updates on this one?

from fragnav.

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

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

from fragnav.

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

from fragnav.

@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

from fragnav.

@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.

from fragnav.

@jakoss Thank you!

from fragnav.

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

from fragnav.

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'

from fragnav.

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

from fragnav.

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

from fragnav.