-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
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
Migrate Artifacts to Another Repository #76
Comments
Many libraries of Google are still in jCenter. I think we should wait until their library migrations. |
Is there any workaround for this? |
@commonsguy Do you know perhaps of a similar library that offers the same but is available without jcenter ? I need to be able to handle both animated GIF and WEBP, and be able to get their frames as they are being played. BTW, for some reason your link causes my web browser to download a file "download"... |
JFrog changed their plans a bit. JCenter is not accepting new submissions in May, but they will continue to serve artifacts for the rest of the year. My hope is that they stick to that plan. If so, we have more time.
I have not looked for one. My project's needs are just to play animated WebP (no need to access frames). |
@commonsguy Do you know of a workaround? Is it possible to use Jitpack to import what's here? Or to use aar/jar ? As for alternatives, I think Fresco might be able to do it, but it's a huge library that for some reason I failed to use. |
Sorry, I have never tried setting anything up with Jitpack, so I have no idea.
A copy of the library will be in your Gradle cache ( Or, simply fork this repo and build it yourself. Or, fork this repo and integrate it as a module in your project. Or, see if somebody else forks the repo and opts to maintain this. Or, wait to see if the repo maintainer switches artifact repositories. |
@commonsguy OK thank you very much. I've noticed many forks from here. Wonder if one of them migrated. |
It's a very trivial matter for individual libraries to move their repository from jCenter to mavenCentral. As long as the Google libraries are in jCenter, we have no choice but to use jCenter and there is no workaround. |
@dalinaum But Google already allows to use mavenCentral instead. Download the beta/canary versions of Android Studio, change from jcenter to mavenCentral, update gradle plugin to :
Or to:
And it will allow you to build fine. |
As @AndroidDeveloperLB had asked on reddit how to solve this, here's a how-to workaround for others :)
|
@carstenhag Would it suffice for this case:
Meaning that instead all those 4 lines, I would use a single one? |
No. As long as this issue (#76) isn't closed and you can't get Therefore it doesn't make sense to use the version variable, as you need to download a new verson manually anyway. So you will end up with something like this:
|
@carstenhag So this is the end result, while also not having jcenter? |
The previous solution is a workaround, because this project is currently only provided on jCenter. Once it is also available elsewhere, you can remove this workaround. Hope that cleared it up :) |
@carstenhag I mean that using this workaround, the end result will be as you wrote, while also not having jcenter? |
Yes. |
@carstenhag I can't find the "import jar/aab" option: Android Studio 4.2 Beta 5 |
Use the stable version :) |
@carstenhag I tried what you wrote, and the aar file went to "webpdecoder-2.0.4.12.0" folder (inside the project folder). I switched to beta version of the IDE, and it seems build line you wrote to find it seems incorrect.
And it still couldn't find stuff from there.
Adding the line on step 3 of what you wrote (
|
Well, you need to replace $PROJECTNAME with the name of the project, so |
@carstenhag I don't understand. Suppose the app name is "Xyz", what should be in build.gradle file, if the created folder is as I wrote ("webpdecoder-2.0.4.12.0" in the project folder, not inside the app's folder)? |
@carstenhag OK I think I got it.
It works fine, but for some reason I see this warning :
Any idea what this is? |
Question: what is the new release: Does it mean it has migrated? |
Sorry be late to handle this issue. The library has migrated and published to Maven Central at now. (https://search.maven.org/artifact/com.github.zjupure/webpdecoder). As a change, user should change the group id from |
@zjupure This is the only needed change? Everything else stayed? The package name? Proguard rules ? ... BTW, why do we have to set Proguard rules? Shouldn't it be as a part of the library? I think you should change the readme file to show to use "kapt" instead of "annotationProcessor " , because then you can reach your GlideApp class. |
proguard rules is also inline in the aar. |
So it's inside already? So maybe you should update the instructions, as those aren't needed anymore? |
This library is being published to JCenter. JCenter is being taken down on May 1 2021.
Ideally, this library would migrate to publish its artifacts on Maven Central or some other artifact repository.
Thanks for considering this!
The text was updated successfully, but these errors were encountered: