Update Travis configuration to fix build issues #27
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
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.
Travis builds were not working for either JDK 8 or JDK 9.
JDK 8 builds were breaking because Travis now defaults to using Xenial unless specified and this release does not include any support for JDK 8. The solution is to specify the distribution as
trusty(see discussion here).JDK 9 builds were breaking because Oracle no longer allows for direct downloads and so Travis switched to OpenJDK. This has SSL issues with JDK 9 and JDK 10. The solution was to use JDK 11 (see discussion here).
It seems it is possible to test against JDK 9 by following the instructions here. Is that something we want to do? Or is JDK 8 and 11 sufficient?