tbroyer
commented
5 years ago I think the best way is to actually run the processor in Gradle (see the tests in this project; and you can use the Gradle Tooling API to do that in non-Gradle projects, as the Gradle TestKit is not available as a library on its own).
The problem with doing that in an annotation processor, or Error-prone check, is that this will only work if the processor being compiled uses @SupportedAnnotationTypes rather than overriding getSupportedAnnotationTypes() and the annotation is available in the classpath (or possibly the processor classpath, as a fallback), but if the annotation is on the classpath, chances are that the processor actually overrides getSupportedAnnotationTypes() to use the annotation's .class.getCanonicalName().
Things could be done in a unit-test, but because getSupportedAnnotationTypes() could, at least theoretically, depend on the ProcessingEnvironment, this needs to be done with an actual CompilationTask; and this would still not check that the processor will actually run incrementally.
There could be some kind of test artifact to help run Gradle projects and check for incrementality, but there'd still be some work needed in each project to "expose" their artifacts to the Gradle builds… For Maven, maybe a "gradle-invoker-maven-plugin" à la "maven-invoker-plugin" would be better…
I'm not sure the best way to do this. If the processor is using
@SupportedAnnotationTypesyou could validate in your processor. Otherwise, there are a lot of options. Error-prone check, but that only covers Java and not Kotlin. Some kind of test artifact that checks the values returned bygetSupportedAnnotationTypes()?