-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Regression of Gradle incremental compilation #1315
Comments
Is this an issue with AutoValue or with Gradle? We don't have much Gradle expertise on this project, unfortunately. |
I don't know, the inputs changed which would make sense as newly generated classes added to the classpath. However you would think Gradle would understand why they came about as implicit inputs and not invalidate the compilation unit. Unfortunately the compilation toolchain and that low level interaction is outside of my gradle experience. Probably if we tried something similar like MapStruct would help indicate if this is a bug in the annotation processor or the toolchain. |
I was able to narrow the problem down to my build's configuration, sorry for the noise. I copied an example (jhipster/generator-jhipster#9134) which had the following. The
The proper fix is,
|
@ben-manes you might want to use https://plugins.gradle.org/plugin/com.diffplug.eclipse.apt for proper Eclipse support. |
Thanks! Switching to that did not seem to find the sources, assuming it replaced my snippet. I'll play with it and see if there is some docs that I missed. |
I am observing file overwrites which should have been resolved in AutoValue 1.9 with #1075. It was flagged by a security tool as a possible indicator of a supply chain compromise.
The build scan confirms this as a
stableSources
input change.I reproduced this locally using,
To avoid flukes, I used a resolution strategy to force the dependency to the right version if an old version was transitively referenced. I also tried to remove a convenience extension, auto-builder, in case it broke the incremental build. The above command still showed a rebuild locally.
This is a minor annoyance but it would be nice to have a clean bill of health from security audits.
The text was updated successfully, but these errors were encountered: