Fixed
Status Update
Comments
be...@google.com <be...@google.com> #3
Is this happening with Studio 3.0?
cm...@google.com <cm...@google.com> #4
Note: This worked for me on Windows 7 Pro 32-bit (with Android Studio 2.3.3). Seems like an issue with adt-branding module (which should contain the "/idea/AndroidStudioApplicationInfo.xml" resource).
ni...@gmail.com <ni...@gmail.com> #6
Thank you for this feedback. Your feedback helps make sure Android development tools are great! Given your issues has been resolved I am closing this issue.
cm...@google.com <cm...@google.com> #7
#8 - please let us know how you are applying your annotation processor(s), and if possible we'll add that to our incremental java compilation blacklist so it works out of the box.
You can also disable it by adding android.incrementalJavaCompile=false to the gradle.properties file (which you might need to create) in your root project.
You can also disable it by adding android.incrementalJavaCompile=false to the gradle.properties file (which you might need to create) in your root project.
cm...@google.com <cm...@google.com> #8
Incremental java compilation will be automatically disabled for projects which apply com.neenbedankt.android-apt in the next release.
ni...@gmail.com <ni...@gmail.com> #9
I use mainly Butterknife (and some others lib like DBFlow but same annotations processor), so blacklisting com.neenbedankt.android-apt will probably fixes 99% of those problems.
st...@google.com <st...@google.com>
ch...@google.com <ch...@google.com> #10
Reopening to keep track of the issue. Annotation processors is not yet supported with incremental java compilation. It will depend on changes in Gradle.
We disabled it for project that apply com.neenbedankt.android-apt, so it's no longer a significant issue.
We disabled it for project that apply com.neenbedankt.android-apt, so it's no longer a significant issue.
ag...@gmail.com <ag...@gmail.com> #11
Is there any timeline on this. Do we know if gradle is going to work on incremental java compilation for annotation
r....@gmail.com <r....@gmail.com> #12
Any updates on the issue? Currently there is not benefit of incremental compilation for the most of the projects as they are using annotation processors
id...@gmail.com <id...@gmail.com> #13
There can't be any updates here until the Gradle issue is fixed:
https://issues.gradle.org/browse/GRADLE-3259
If one wishes to speed the process up pls register atissues.gradle.org and vote/comment for the issue there. As it seems that currently Gradle team doesn't care too much about the issue, it's not assigned and it's not on their roadmap yet.
If one wishes to speed the process up pls register at
r....@gmail.com <r....@gmail.com> #14
Looks like this issue will not moving anywhere in the near future. But still exists and affects lots of projects
st...@gmail.com <st...@gmail.com> #15
It's really an issue. Though everyone claims this is hard problem, it looks like JRebel has managed to do it:
https://zeroturnaround.com/rebellabs/speeding-up-android-builds-with-an-incremental-java-compiler/
Does anyone know how well their approach works ?
Does anyone know how well their approach works ?
ia...@gmail.com <ia...@gmail.com> #16
The gradle issue has been moved to github: https://github.com/gradle/gradle/issues/1320
Comment and vote there now.
Comment and vote there now.
je...@google.com <je...@google.com> #17
This has been delivered starting in AGP 3.2
eh...@gmail.com <eh...@gmail.com> #18
Comment has been deleted.
Description
This means we have to disable the incremental java support for many apps that otherwise seem to follow "Android best practice".