diff options
author | Abhijit Kulkarni <akulk022@ucr.edu> | 2023-11-09 15:56:25 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-11-09 15:56:25 -0800 |
commit | 0141aca22138e479dfcbc4acdb56211ca4e17d73 (patch) | |
tree | a2ebcef3dc496278ce330ebc2cb9f1200585d559 | |
parent | 5aeb32cc0f310a4789c0ba47b790e2f7737db810 (diff) | |
download | nullaway-0141aca22138e479dfcbc4acdb56211ca4e17d73.tar.gz |
JSpecify: adding com.google.common to annotated packages in build.gradle (#857)
Based on the fixes made in #856 , we should no longer get that exception
after adding com.google.common in the annotated packages when running in
JSpecify mode.
-rw-r--r-- | nullaway/build.gradle | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/nullaway/build.gradle b/nullaway/build.gradle index 8000dbc..90ac062 100644 --- a/nullaway/build.gradle +++ b/nullaway/build.gradle @@ -152,7 +152,7 @@ tasks.register('buildWithNullAway', JavaCompile) { sourceSets.main.compileClasspath) options.errorprone.enabled = true options.errorprone { - option("NullAway:AnnotatedPackages", "com.uber,org.checkerframework.nullaway") + option("NullAway:AnnotatedPackages", "com.uber,org.checkerframework.nullaway,com.google.common") option("NullAway:CastToNonNullMethod", "com.uber.nullaway.NullabilityUtil.castToNonNull") option("NullAway:CheckOptionalEmptiness") option("NullAway:AcknowledgeRestrictiveAnnotations") |