Can I apply ksp gradle plugin from my own gradle plugin?

# ksp

[Robert Jaros]

Can I apply ksp gradle plugin from my own gradle plugin?

[Javier]

yes you should be able

[Robert Jaros]

I've tried project.pluginManager.apply("com.google.devtools.ksp") and it does seem to work without errors, but not fully correct (some tasks are missing and I can't apply ksp to my mpp targets).

[Javier]

which errors and how are you applying your plugin

[Robert Jaros]

My plugin is applied with plugins { id("...") } block

[Javier]

there should be no difference between that and applying ksp directly

[Javier]

if you are using the same version and so on

[Robert Jaros]

E.g. when applying directly I see three tasks:

kspCommonMainKotlinMetadata
kspKotlinBackend
kspKotlinFrontend

but when applying indirectly I see only one of them: kspKotlinFrontend

[Javier]

maybe you are combining your plugins in your convention plugin in a way it is not detecting that kmp is enabled or something so

[Javier]

you can confirm that by having the same setup and only applying ksp in your convention plugin

[Robert Jaros]

When applying directly it works:

dependencies {
    add("kspCommonMainMetadata", "myprocessor")
    add("kspFrontend", "myprocessor")
}

[Javier]

I have seen issues with plugin orders before with Kotlin Gradle plugin for example

[Robert Jaros]

When indirectly I have an error:

> Configuration with name 'kspFrontend' not found.

[Javier]

kmp plugin is applied by your convention plugin too?

[Javier]

or directly

[Robert Jaros]

The same setup - I've just commented id("com.google.devtools.ksp") version "1.7.0-1.0.6" in my plugins {} block

[Javier]

that is weird

[Robert Jaros]

kotlin plugin is applied directly

[Javier]

check if the kgp/ksp versions are correct

[Javier]

maybe it is taking a different version from the classpath

[Robert Jaros]

I'll try to check this configuration step by step once again - perhaps I'm missing something obvious

[Javier]

you convention plugin is a precompiled one?

[Robert Jaros]

yes

[Javier]

apply ksp in the plugins block in your precompiled plugin instead of with the manager

[Robert Jaros]

I've managed to make it work. I've applied the plugin with plugins.apply("com.google.devtools.ksp") line and then applied it to my source sets with:

dependencies {
            add("kspCommonMainMetadata", "myprocessor")
        }

        afterEvaluate {
            dependencies {
                add("kspFrontend", "myprocessor")
            }
        }

[Javier]

I would apply the plugins in the plugins block in precompiled plugins instead of with apply

[Robert Jaros]

I have no idea why common can't be in the afterEvaluate block as well and why kspFrontend needs to (doesn't work without it)

[Robert Jaros]

Tried with the plugins block but it doesn't work (or I don't know how to do it 😉)

[Javier]

that is weird

[Javier]

is your project open source?

[Robert Jaros]

Yes. But it's quite large and complicated (KVision).

[Javier]

is there a branch where you are trying these things?

[Robert Jaros]

I'll publish the branch in a moment

[Robert Jaros]

https://github.com/rjaros/kvision/tree/ksp/kvision-tools

[Robert Jaros]

my plugin and processor are in the kvision-tools dir

[Robert Jaros]

This is currently working fine for me but I'll be grateful for any advice how to make it better :)

[Javier]

where is the precompiled plugin??

[Javier]

I think we missunderstood

[Javier]

I was thinking you had a precompiled convention plugin, but looks like it is a normal convention plugin

[Robert Jaros]

Yep, I have a normal plugin not a precompiled one. Sorry for misleading. I'v just googled what a precompiled gradle plugin is 😉