Has anyone had luck with writing a kotlin subplugin with Gradle's TestKit? They don't seem to be happy together, because of the ServiceLoader logic that SubpluginEnvironment does with class loaders. I see that even Kotlin's tests don't use TestKit. 😞 I'd love to have a TestKit based test for a compiler plugin I'm writing.

TestKit might create some classloading issues when using

runner.withDebug(true)

, it should not cause trouble when not using that

what is the difference between a plugin and subplugin?

it’s not a Gradle thing the Kotlin Gradle Plugin has a notion of “sub plugin”

Subplugins is a Kotlin gradle plugin concept. It wants to load the compiler plugins, and it uses a ServiceLoader to do it. Then uses the Subplugins to tied the configuration in the Gradle plugin to the corresponding compiler plugin.

I see.

I've only got online one SO post, so that is quite a coincidence. 🙂

@eskatos I concur that debug changes things. When I run without debug, I get identical behavior though, as in it never sees my subplugin. It could be for another reason, but it's suspicious.

it is suspicious fwiw, TestKit without

withDebug

just runs a regular Gradle daemon

Thanks @eskatos. I remember the days of publishing to a local repo for testing. I'll give it a try to unblock myself. For an issue, there's a few pieces involved. I'll see if I can pair down the minimal project I'm working with: https://github.com/quidryan/debuglog/blob/plugin-unit-tests/gradle-plugin/src/test/kotlin/debuglog/DebugLogGradlePluginTest.kt It's from a small addition to @kevinmost’s debuglog example project.