-
Notifications
You must be signed in to change notification settings - Fork 299
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 error when adding NullAway 0.1.7 to Android projects #48
Comments
I didn't find a fix yet |
Ah, I know what this is. The problem is that an old version of Google Java Format didn't shade its internal javac correctly (see google/google-java-format#169). This is fixed as of GJF 1.4. @yaroslav-shlapak can you change your
|
Alternately, I think updating |
@msridhar by this
did you mean something like this
to forcefully resolve versions conflict? I've tried solutiions with dagger version 2.12 and forced dependencies resolving - they both work. Dependencies tree check:
and
Thank you for fast and helpful response!:+1: |
The only disadvantage with forcing dependencies is it will force a downgrade if/when other libs pull in an even more recent version of GJF (1.5 has been released). If you just add a dependence on 1.4 that should lead to the upgrade but not the downgrade. All that said, in this case probably bumping to Dagger 2.12 is the best solution, if that works for you. Please let us know if you have other issues! |
Whenever NullAway runs, it must be loaded via Error Prone. Hence, I believe that the Error Prone Check APIs should always be available. Making the errorProneCheckApi a compileOnly dependence should reduce the size of the annotation processor classpath in some cases, which could speed up builds and avoid some incompatibilities like in #48.
I'm getting the gradle build error when adding NullAway version 0.1.7 to different projects in Android Studio 3.0 and gradle plugin version 3.0.0.
Commenting out
leads to successful build.
Project level build.gradle:
App level build.gradle:
Error stacktrace
The text was updated successfully, but these errors were encountered: