Repository navigation
Help popular auto value extensions adopt incremental processing #673
Description
- auto-value-parcel: Merged
- auto-value-gson: Merged
- auto-value-cursor: Supported since 2.0.0-rc1
- paperparcel: Open issue
- auto-value-moshi: Merged
- auto-value-redacted: Supported since 1.1.0
- auto-value-with: Supported since 1.1.0-rc1
Activity
- changed the title
[-]Help popular auto value extension adopt incremental processing[/-][+]Help popular auto value extensions adopt incremental processing[/+]on Oct 29, 2018 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).
Reacted by BingranI 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.
Reacted by Bingranauto-value-with 1.1.0-rc1 and auto-value-cursor 2.0.0-rc1 are on their way to maven central. Both are
ISOLATING.@gabrielittner Great, thanks!!
auto-value-gson, auto-value-moshi, and auto-value-parcel all support this now (extensions are
ISOLATINGand the factory processors areAGGREGATING), and will be in their next releasesauto-value-redacted is
ISOLATINGnow. auto-value-bundle is removed from the list since it is not released.People, what about AutoFactory?
