-
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
Help popular auto value extensions adopt incremental processing #673
Comments
Here's an associated issue on gradle/gradle: gradle/gradle#5277 |
Fwiw, autovalue extensions are not processors themselves. There's a new API in 1.6.3rc1 to be implemented by extensions: http://static.javadoc.io/com.google.auto.value/auto-value-annotations/1.6.3rc1/com/google/auto/value/extension/AutoValueExtension.html#incrementalType-javax.annotation.processing.ProcessingEnvironment- |
Yeah, our goal is to let extensions figure out if they are compatible with incremental processing and implement that new API. |
I'll look into my two extensions later this week (with and cursor). |
I meant: the open issues linked above (auto-value-gson and auto-value-gson) don't talk about the AutoValueExtension API, they only link to Gradle's documentation. |
auto-value-with 1.1.0-rc1 and auto-value-cursor 2.0.0-rc1 are on their way to maven central. Both are |
@gabrielittner Great, thanks!! |
auto-value-gson, auto-value-moshi, and auto-value-parcel all support this now (extensions are |
auto-value-redacted is |
People, what about AutoFactory? |
PaperParcel supports incap since 2.0.7, see changelog. |
@bejibx Thanks for great work! I am closing this issue because all of the popular auto value extensions support incremental annotation processing! Thanks everyone! |
The text was updated successfully, but these errors were encountered: