You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem we face is that for some unknown (at least to me) reason, the kspKotlin Gradle tasks depends on the generateProto task as soon as the protobuf plugin is added to the module. Please run ./gradlew :workload:kspKotlin --dry-run in the provided minimal example to reproduce.
Strangly the dependency disappears when changing the main/java source set reference in the affected module, e.g., add
sourceSets {
main {
java {
setSrcDirs(srcDirs)
}
}
}
to the workloadbuild.gradle.kts file.
Is this expected behavior? Versions 0.8.x do not have this issue.
In our (more complicated) build we additionally enforce that proto buffers are generated before running ksp which leads to a cyclic task dependency.
The text was updated successfully, but these errors were encountered:
Please see the minimal example here: https://github.com/schmist/ksp-proto-minimal and my comment here: #624
The problem we face is that for some unknown (at least to me) reason, the
kspKotlin
Gradle tasks depends on thegenerateProto
task as soon as the protobuf plugin is added to the module. Please run./gradlew :workload:kspKotlin --dry-run
in the provided minimal example to reproduce.Strangly the dependency disappears when changing the
main/java
source set reference in the affected module, e.g., addto the
workload
build.gradle.kts
file.Is this expected behavior? Versions 0.8.x do not have this issue.
In our (more complicated) build we additionally enforce that proto buffers are generated before running
ksp
which leads to a cyclic task dependency.The text was updated successfully, but these errors were encountered: