Update build.gradle to prevent guava conflicts #34
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
2 tasks
|
Afaics, it is still used to support Java 5 applications. According to the issue reported here: googleapis/google-api-java-client#903 (comment) Overriding with guava 18 or 19 should be safe. |
|
Added a small comment in a separate commit then released :-) https://github.com/MovingBlocks/CrashReporter/releases/tag/v4.0.1 |
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.
com.google.apis:google-api-services-drive:v2-rev193-1.20.0depends onguava-jdk5, which is no longer maintained as well as causes conflicts with vanilla guava when run with Terasology due to there being multiple instances of guava on the classpath. This is also mentioned in MovingBlocks/Terasology#2584.This PR fixes the issue by excluding
guava-jdk5and instead including vanilla guava in the cr-core build.gradle.