Should "kotlinCompilerPluginClasspath" still work ...
# compiler
c
Should "kotlinCompilerPluginClasspath" still work in Kotlin 2.x+ Or do we have to use a SubPlugin (and if so how is that even possible to create compiler/plugin/consume in the same project without publishing to maven(local)?)
j
The classpath still works. We use it in a few places.
In general I prefer building the Gradle plugin both in the main build and a nested project like build-support
This lets me use the plugin in the same repo
c
Mmm, interesting, I have tests checking the compiler works and generates the properties (at least at a test level). I added messaging for the registrar and looks like it's not registering the plugin during compilation, hopefully I just missed something dumb then
j
c
Interesting, it is calling
registerExtensions
but then never calls
generate
in the extenstion
j
Are there actual sources being compiled?
c
I just attach properties to files with annotation on it
Oh I'm not using a transformer, wondering if thats why
Would have hoped the tests failed 😕
Oh found out the issue, it's running the plugin after the first pass of files, so throwing compiler warnings before it's run. I probably missed it, but I need to tell the compiler "I'm going to generate these properties"