We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi!
I've the question about if is possible to move the version1.0-alpha05 to mavenCentral. Link -> https://mvnrepository.com/artifact/com.leinardi.android/speed-dial Actually it's only new version but not the version that we use, is it possilbe to move?
The reason about this change is the notice of obligation to migrate all repositories to mavenCentral. Link : https://developer.android.com/studio/build/jcenter-migration
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Hi @CarlosVF2, unfortunately there is no plan to migrate older versions of the library to MavenCentral, but the latest and newer versions will use it.
If you need to use an older version, you can get it via JitPack: https://jitpack.io/#leinardi/FloatingActionButtonSpeedDial/1.0-alpha05
But, if I may ask, why are you using version 1.0-alpha05? It is really old.
1.0-alpha05
Sorry, something went wrong.
Hi @leinardi ,
At first, thanks a lot for your answer. The reason why we are using that version is for the compatibility.
We will consider your answer to use jitpack.
Again, thanks a lot.
No branches or pull requests
Hi!
I've the question about if is possible to move the version1.0-alpha05 to mavenCentral. Link -> https://mvnrepository.com/artifact/com.leinardi.android/speed-dial
Actually it's only new version but not the version that we use, is it possilbe to move?
The reason about this change is the notice of obligation to migrate all repositories to mavenCentral. Link : https://developer.android.com/studio/build/jcenter-migration
Thanks in advance!
The text was updated successfully, but these errors were encountered: