-
Notifications
You must be signed in to change notification settings - Fork 95
fix(android): migrate away from JCenter #278
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm approving it with the blind faith that CI will just go smoothly 🤞
Android Gradle Plugin has a dependency on |
Allright, as basically we expected, by moving away from jcenter() we are hitting the infamous:
For which all the workarounds on StackOverflow are literally to revert the change: move from Now. Here's the situation:
So here the alternatives:
If neither of those are viable, it's gonna be a fun ride. Let's throw some ideas:
This will mean that only new releases of React Native will survive - even if we went back and patched ex. 0.61, 0.62, 0.63 with this change, previous versions/not-latest patches will all break. Also, this will still require all the developers that have a RN app to change their code too to remove the jcenter() reference. PS: in all of this I haven't even considered if this is trove4j is also being used by some third party package, in which case it will be even more fun 💀 EDIT: As pointed out by @arazabishov, I could actually confirm that trove4j is not actually used directly in the React Native codebase. That said, there are a few reference to jcenter across the code that will need to be removed (I am not sure these will directly affect any given existing RN app). |
Running See the logs results--- com.android.tools.lint:lint-gradle:26.6.0 kotlinCompilerClasspath kotlinCompilerPluginClasspath kotlinKaptWorkerDependencies kotlinKlibCommonizerClasspath EDIT: @kelset, to put the logs into details tag. |
Another thing to keep in mind is that Gradle spits out errors 1 by 1 while trying to resolve dependencies. We don't know if any other libraries are missing on Since the shutdown of jCenter() will break all Android builds in the world, I suggest that we wait until Google provides a solution to this problem 🤠 |
Update on the Google side - I went into the deep end and git clone'd the Android platform source code to see how things are there - via It looks like they already migrated from But I don't know if that trove4j is also used somewhere else. |
39f6476
to
107db5e
Compare
107db5e
to
55f96b9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting idea to force the resolution to use the new intelliJ version! I really like it 👍
🎉 This PR is included in version 0.5.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
JCenter is being sunset: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/
Platforms affected
Test plan
CI should pass.