You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now gradle complains that org.dominokit.jacksonapt.processor.ObjectMapperProcessor is not incremental and a full recompilation is required.
Task :compileJava
Build cache key for task ':compileJava' is 8832ef9fce86b8122d4f38033a68122b
Task ':compileJava' is not up-to-date because:
Input property 'stableSources' file /Users/fsousa/Projects/demo/gwt-jackson-demo/src/main/java/pt/ipb/demos/gwt/jackson/client/Main.java has changed.
Created classpath snapshot for incremental compilation in 0.001 secs.
Class dependency analysis for incremental compilation took 0.001 secs.
Full recompilation is required because org.dominokit.jacksonapt.processor.ObjectMapperProcessor is not incremental. Analysis took 0.002 secs.
Task :compileJava
Build cache key for task ':compileJava' is 8832ef9fce86b8122d4f38033a68122b
Task ':compileJava' is not up-to-date because:
Input property 'stableSources' file /Users/fsousa/Projects/demo/gwt-jackson-demo/src/main/java/pt/ipb/demos/gwt/jackson/client/Main.java has changed.
Created classpath snapshot for incremental compilation in 0.001 secs.
Class dependency analysis for incremental compilation took 0.001 secs.
Full recompilation is required because org.dominokit.jacksonapt.processor.ObjectMapperProcessor is not incremental. Analysis took 0.002 secs.
Thanks.
The text was updated successfully, but these errors were encountered:
I believe, but am not certain, that this process cannot qualify for any incremental mode. It might be possible to be marked as aggregating, but even that could depend on whether or not json beans are actually present as sources (and can be used as originating elements in aggregating) or are elsewhere on the classpath (separate modules, which then need to re-trigger building this module and fully running the processor).
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"?
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: