I have an annotation processor that I want to include in my build convention plugin. Since this needs classpath access as well, my "go-to" solution was to have two modules, a "annotation-processor-lib" module (applying the

java-library

plugin) and an "annotation-processor" build convention that just has

dependencies { "kapt"("my.group.name:annotation-processor-lib") }

in it. I guess it's not possible to easily combine both modules into one, i.e. having a plugin who can be set up as annotation-processor, is it? Or is there some API that would allow for this?

Some of those use cases are the reason I would prefer an approach similar to the Slack plugin over multiple convention plugins • https://github.com/slackhq/slack-gradle-plugin