Skip to content
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

Make Guava dependence explicit #120

Merged
merged 1 commit into from
Feb 4, 2018
Merged

Conversation

msridhar
Copy link
Collaborator

@msridhar msridhar commented Feb 3, 2018

See #119. Error Prone does not expose its packaged Guava on Bazel. NullAway does indeed rely on Guava, and this will make it work better out of the box on Bazel. Eventually, we can think about shading or getting rid of this dependence, but this is a first step.

@@ -34,7 +34,7 @@ def build = [
checkerDataflow : ["org.checkerframework:dataflow:${versions.checkerFramework}",
"org.checkerframework:javacutil:${versions.checkerFrameworkNAFork}"],
gradleErrorPronePlugin : "net.ltgt.gradle:gradle-errorprone-plugin:0.0.8",
guava : "com.google.guava:guava:21.0",
guava : "com.google.guava:guava:22.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make it 24.0-jre?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm trying to minimize potential incompatibility with other annotation processors. If we decide to shade Guava I'll bump higher

@msridhar msridhar merged commit caeb60c into master Feb 4, 2018
@msridhar msridhar deleted the explicit-guava-dependence branch February 4, 2018 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants