This message was deleted.

You should wire it to neither task. Instead you should define the generation task's output as source directory, then all tasks that need sources automatically get the necessary task dependency. Otherwise, you need to add explicit task dependencies to all tasks that need the sources and that could be added by arbitrary plugins.

val yourGenerationTask by tasks.registering...

sourceSets {
    main {
        java {
            srcDir(yourGenerationTask)
        }
    }
}

I am going to try that, thank you! I guess it would work with Kotlin APIs too? thinking in the kotlin custom dsl for KMP as root source sets don't work on kmp

🤷‍♂️

Executing

./gradlew compileKotlin --dry-run

should show the task if it was added as

srcDir

?

Probably

yeah, on kotlin jvm, the Gradle official source sets are mapped to the Kotlin ones, but with kmp the sets are empty but the kotlin ones have the info

If it does not work on those, I'd say you should report that, so they can fix that.

I am getting a stack overflow because I am getting the kotlin generated dir from the kotlin src dirs, and I am setting the task as input of a kotlin source set. Is there any strategy for this use case? I would want to avoid hardcoding the generated dir and instead filter based on the existents ones

I'm not fully getting. Do you mean your generation depends on the other source files?

From other part, it is added to the kotlin source dirs of the

main

set the directory

build/generated/main

(or whatever) In order to be able to use it on the task, I am getting it from the kotlin extension too. This mix is generating a stack overflow

I'm still not fully getting. But it sounds like you try to generate into a common folder. Don't do that. Never, ever, ever, ever have tasks with overlapping outputs.