Hey <@UVAR0DXP0>. I think you should change your d...

# kotest

[Alexander Ioffe]

Hey @Emil Kantis. I think you should change your docs to tell folks to add KSP before kotest.
Otherwise the build fails and it throws an error that has nothing to do with the problem at hand.

When I do this:

plugins {
  ...
  alias(libs.plugins.kotest)
  id("com.google.devtools.ksp") version "2.2.0-2.0.2"
}

Instead of this:

plugins {
  ...
  id("com.google.devtools.ksp") version "2.2.0-2.0.2"
  alias(libs.plugins.kotest)
}

This happens:

An exception occurred applying plugin request [id: 'io.kotest', version: '6.0.0']
> Failed to apply plugin 'io.kotest'.
> KSP neither found in root project nor exoquery-runner-core, please add 'com.google.devtools.ksp' to the project's plugins

[Alexander Ioffe]

What's even worse is that the AI just regurgitates the utterly useless information:

[sam]

@Alexander Ioffe in all the sample projects, ksp is added after, so there must be something odd with the timing. Do you have a simple use case I can look at ?

[Alexander Ioffe]

I ran into this in my project ExoQuery. It's a multi-module where I've got:

ExoQuery
├── build-logic
├── exoquery-engine          (tacked-on via includeBuild)
├── exoquery-plugin-gradle   (tacked-on via includeBuild)
├── exoquery-plugin-kotlin   (tacked-on via includeBuild)
├── exoquery-runner-android
├── exoquery-runner-core
├── exoquery-runner-jdbc      <-- Kotest+KSP here
├── exoquery-runner-native
└── testing                   <-- Kotest+KSP here

I never had KSP on the base-level and I don't know if my unique project structure has anything to do with it.

[Alexander Ioffe]

I saw the issue in the testing project and in exoquery-runner-jdbc.

[sam]

thanks, I will get on this tomorrow and figure it out, thanks for the repo !