This message was deleted.

You should start with removing all these bad practices, like using

allprojects { ... }

,

subprojects { ... }

,

apply plugin

,

ext

, ... which are highly discouraged and you should use other things like for example convention plugins instead. Or also

...Compatiblity

and instead use JVM toolchains. But anyway, if I got you right, you have in

commons

the plugin and also some libraries and the libraries should be Java 17 while the plugin should still be Java 11? How should that work if you declare all subprojects ot be 11 or 17? Again, convention plugins would solve the problem, as you apply them only where you actually want their effect and not like a watering can. But you can of course also add some more bad practice and set the values depending on the project name in the

subprojects

closure.

@Vampire you got it right, while building and publish plugin i want it to be applied as compatible with Java 11 where as Commons module is on jdk 17..I have tried setting the compatibility in the subprojects of plugin.gradle and couldn't achieve the result. I was facing issue i specificed above.

Well, you did not provide enough concrete information for me to draw any conclusion where you did what. Can you provide an MCVE?

Sure @Vampire will get back with MCVE