Should "kotlinCompilerPluginClasspath" still work ...

# compiler

[chrisjenx]

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)?)

[jw]

The classpath still works. We use it in a few places.

[jw]

In general I prefer building the Gradle plugin both in the main build and a nested project like build-support

[jw]

This lets me use the plugin in the same repo

[chrisjenx]

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

[jw]

Here's a place we're still doing it https://github.com/cashapp/zipline/blob/trunk/zipline%2Fbuild.gradle.kts#L36-L37

[chrisjenx]

Interesting, it is calling registerExtensions but then never calls generate in the extenstion

[jw]

Are there actual sources being compiled?

[chrisjenx]

I just attach properties to files with annotation on it

[chrisjenx]

Oh I'm not using a transformer, wondering if thats why

[chrisjenx]

Would have hoped the tests failed 😕

[chrisjenx]

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"