Support Gradle Incremental Annotation Processing

It would be nice if crumb would support incremental annotation processing released in Gradle 4.7. Given that crumb uses resources, it doesn’t look like that’s going to work. See https://docs.gradle.org/4.7/userguide/java_plugin.html#sec:incremental_annotation_processing

A similar project I work on solves a similar problem (with a million times less flexibility). The library TLDR is this:

• The composite equivalent of CrumbProducer generates a class with an annotation on it.
• The composite equivalent of CrumbConsumer looks for the generated classes annotated by the step above

I think an approach similar to this would allow the crumb annotation processors to be incremental.

This would essentially change the implementation details within crumb to use classes (again, that can be proguarded out) instead of resources.

I’d be willing to help/do the work for this if it’s a direction that the library maintainers deem appropriate.

[ZacSweers]

Nice. I can take a look at this sooooon-ish

On Mon, Mar 25, 2019 at 6:40 AM Jay Newstrom [e-mail] wrote:

Looks like this support just got merged in! gradle/gradle#8797 https://github.com/gradle/gradle/pull/8797

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/uber/crumb/issues/33#issuecomment-476201231, or mute the thread https://github.com/notifications/unsubscribe-auth/ABTEvkPJnCdoptI8t3PZJ4xv7Y23GSqZks5vaNG8gaJpZM4T7pk2 .

[ZacSweers]

Yep that’s the one! Let’s touch base again once that’s available