-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Remove JCenter when possible #5843
Conversation
This comment has been minimized.
This comment has been minimized.
@TobiGr, try pulling groupie from jitpack! I have done it at my own fork.. |
Also exoplayer from google's repo |
@TobiGr So I think we can drop Also somehow the build seems to be messed up. Maybe rebase? |
Friendly reminder that this is still a thing. |
Build failure is due to
Exoplayer 2.12.3 is not published at https://maven.google.com/: Only versions >= 2.13.3 are |
All dependencies which were fetched from JCenter are now available via Maven Central. This source change is necessary becuase JCenter announced they werer going to be read-only starting at 31st March 2021 (https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter).
ExoPlayer is now on |
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.
Everything is green 🥳
What is it?
Description of the changes in your PR
The JCenter repository is going to be shut down. This PR tries to resolve as many dependencies as possible from other repositories.
Fixes the following issue(s)
#5837
APK testing
On the website the APK can be found by going to the "Checks" tab below the title and then on "artifacts" on the right.
Due diligence