-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Gradle: ObjectMapperProcessor is not incremental, full recompilation is required #30
Comments
I believe, but am not certain, that this process cannot qualify for any incremental mode. It might be possible to be marked as That said, if mapstruct (see mapstruct/mapstruct#1420, mapstruct/mapstruct#1971, mapstruct/mapstruct#1414) is able to support this without caveats, it may be possible. From the link, I don't see what a processor should do to explicitly opt-out - for example if it uses a compiler task/plugin, how would it say "no, I actually need to re-run if my files change in any way, not just their API"? |
I don't know the internals of domino-jackson, but google dagger is fully incremental. There is already an incremental gwt module that supports isolation: When the GWT migration is completed, I suppose there will be many modules that uses the annotation processor and that can make the compile task time consuming. I think gradle is smart enough to know what needs to be compiled. |
Is it possible to make the annotation processor incremental?
https://docs.gradle.org/current/userguide/java_plugin.html#sec:incremental_annotation_processing
Right now gradle complains that
org.dominokit.jacksonapt.processor.ObjectMapperProcessor
is not incremental and a full recompilation is required.Thanks.
The text was updated successfully, but these errors were encountered: