Hi, I have a clean test project, where I planned to play with ByteBuddy.
I did a minimum setup, added plugin and dependency, defined transformation plugin, but gradle unable to reference plugin class from the source code of the one root project. Unfortunately I have no idea why.
May be you know.
Besides that you should never use the Spring Dependency Management plugin (it is a relict from times when Gradle did not have built-in BOM support, by now does more harm than good, and even its maintainer recommends not to use it anymore but the built-in BOM support using platform(...)), you forgot to mention the exact error message you get, optimally in form of a build --scan URL.
Ah, now I see what you mean.
Yeah, how should that ever work?
To build the source within src/main/java you need the build script executed.
But you try to use something you build within src/main/java from within your build script.
But to use it you first have to build it.
But to build you want to use it.
See where that leads to?
Whether this is generally the right approach has nothing to do with Gradle, that you have to check with ByteBuddy.
But if that is how you are supposed to use such a class, then you probably have to split your build into two builds that you can then combine using composite build.
One where you build your plugin class that is included by the other build which could then use the classes from that build if you declare a buildscript dependency or apply a plugin that you also build in that project.
Got it. Thank you very much for the clarification!
1 Like