This message was deleted.

You can probably use dependency resolution rules to enforce a different version.

I use

compileOnly

for the plugins in my convention plugin, so that each project that uses it has to supply the dependency as well. As long as the different versions are ABI compatible it works.

But that would be against the intention. What do you win if you have to add the plugins to the classpath when all the convention plugin is doing, is to apply them. If you react to plugins being applied and it should work without them,

compileOnly

is great. But for the given case I don't think it will help much.

True, I missed that point