-
Notifications
You must be signed in to change notification settings - Fork 226
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
Gradle 5.x #330
Gradle 5.x #330
Conversation
For the life of me I don't understand this lint/gradle error. Continues to happen even if I manually create that configuration too |
Fwiw, the warning in |
Yep, I was just noting that they're coming from the plugin and not something we can completely resolve yet |
Not ready yet because we need a newer version of AGP
Resolves #293
@@ -1,5 +1,5 @@ | |||
distributionBase=GRADLE_USER_HOME | |||
distributionPath=wrapper/dists | |||
distributionUrl=https\://services.gradle.org/distributions/gradle-4.10.2-all.zip | |||
distributionUrl=https\://services.gradle.org/distributions/gradle-5.2.1-all.zip |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like they just released 5.3
Now lint OOMs CI. -_- |
@lazaroclapp @msridhar any ideas about that NullAway wiring failure?
|
You changed from configuring every |
Yep just realized that in trying to repro this on the nullaway sample. Is there a way to disable nullaway for those variants though? I know only running a subset of error prone checks in tests is a pattern some projects use, but it seems like that may not be possible if it's always initialized just for being on the classpath |
Either only put NullAway in the classpath for non-test variants ( afterEvaluate {
tasks.withType(JavaCompile).configureEach {
options.errorprone {
if (compilingTestOnlyCode) {
check("NullAway", CheckSeverity.OFF)
}
}
}
} (or alternatively using I would however configure |
BTW (seeing your last commit), tasks.withType(JavaCompile).configureEach {
options.errorprone.nullaway.severity = provider { options.errorprone.compilingTestOnlyCode ? CheckSeverity.OFF : CheckSeverity.ERROR }
} (Fwiw, I've just updated |
Yep I agree with putting it in every variant normally. Thanks for the example, continuing that thread in uber/NullAway#294 Unfortunately even if I manually wire this for each of those variants in 0916401, the error still comes up. Will dig in more as I'm not sure where else this could be configured unless |
confirmed locally that |
We only need it for snapshots, PRs can be built separately
@shaishavgandhi05 want to re-review this since it's changed a fair bit now? |
I've also tweaked the travis CI settings to only run branch builds on master (for snapshots) and limit PR builds to just the single PR build type |
compilationHelper.setArgs(ImmutableList.of("-XepOpt:TypesWithScope" | ||
+ "=com.uber.autodispose.errorprone.ComponentWithLifecycle")); | ||
compilationHelper.addSourceFile("UseAutoDisposeDefaultClassPositiveCases.java").doTest(); | ||
@Test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why the annotation on separate line? All other tests have it on the same line right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Going to start slowly transitioning this to GJF, started with this
Modernizes the android example with the new lazy task configuration APIs. Based on implementation figured out here: uber/AutoDispose#330
Resolves #296
Note there's still some warnings about accessing compiler APIs, but that's internal to the error prone plugin. Will need to wait for tbroyer/gradle-errorprone-plugin#22