@st_oehme this doesn’t seem to be working for me.
I have configured the annotationProcessorPath for my compile task, and I am using some other code provided in this thread by @mark_vieira to inspect the effectiveAnnotationProcessorPath to make sure that only the jars I have added to the annotationProcessorPath are being included. That’s working correctly. When I run the compile, the code provided by Mark correctly shows the jar file that has the annotation processor and no other jars.
However, gradle is also telling me that the compile is not incremental because annotation processors are found:
`:ComBase:Common:compileJava - is not incremental. Annotation processors are present.`
I’m using 3.4-rc-3. My reading of the docs suggests that I’m doing this correctly.
I don’t know if this information is relevant, but in case it is:
- The processor jar is the same jar that contains the annotation to be processed. This necessarily places a compile-time dependency on that jar so that we can actually apply the annotation. I have created a separate jar that contains ONLY the annotation, and that jar is on the compile path. The processor jar still has the annotation class. This means the annotation itself will be found twice.
- Also, the main code has a compile time dependency on a library that the processor needs at runtime. That library is therefore duplicated in the apt config as well as the compile config.
Any help would be appreciated,
Thanks