It looks like javac defaults to only showing 100 errors. You have to
increase that limit by adding a compiler option. With databinding and a
couple other code generation tools, I had over 100 errors if it failed.
Add this in build.gradle to see up to 500.
gradle.projectsEvaluated {
tasks.withType(JavaCompile) {
options.compilerArgs << "-Xmaxerrs" << "500"
}
}
On Tuesday, July 19, 2016 at 11:15:03 AM UTC-6, Austyn Mahoney wrote:
>
> I am using the `apt` gradle configuration (android-apt) for all the
> annotation processor dependencies in my app.
>
> Whenever I am messing around with my Modules and Components, I sometimes
> need a Dagger annotation processor error message to figure out what is
> going on. The problem is, whenever I compile with an incorrect Dagger setup
> I get error messages unrelated to the root cause. The error messages given
> in Android Studio are just missing symbol errors because the annotation
> processing did not finish.
>
> Compiler error messages:
>
> error: cannot find symbol class DaggerApplicationComponent
>
> or
>
> {redacted}/app/src/main/java/{redacted}/ProfileSettingsFragment.java
> Error:(7, 50) error: package {redacted}.databinding does not exist
> Error:(16, 9) error: cannot find symbol class
> FragmentProfileSettingsBinding
>
> This databinding symbol error is then repeated about 100 times, and the
> actual problem that made the annotation processing fail is nowhere to be
> found.
>
> Is this the right place to be asking something like this, or is this
> related to my build setup somehow? If not, is there some way to get Android
> Studio to display the actual root cause, rather than the missing symbol
> errors?
>
--
You received this message because you are subscribed to the Google Groups
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
