Update .travis.yml to use JDK 17 and target SDK 34
#77
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MGaetan89
force-pushed
the
fix_travis_build
branch
from
5dc61dd to
c477423
Compare
|
this fixes CI back to the same (failing) state as 3 months ago, and enables fixing further broken pipeline |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm not too familiar with Travis CI, so there might be better ways to make it work. But at least the build starts now.
The issue now is that the
com.google.android.exoplayer:exoplayer:2.8.4package cannot be found.It doesn't seem to exist on jCenter and is not available on Google's Maven repository either.
Maybe it should be updated to the latest version (2.19.1) or migrated to AndroidX Media3.