Closed Tapchicoma closed 3 weeks ago
Commit with incorrect work of plugin
Hello, could you say if there is some progress on this issue? It is currently blocking me from upgrade allmy projects up to kotlin 2.0 and the lates compose :(
@InsanusMokrassar the proper fix is in progress.
In the meantime, your project doesn't seem to use js legacy target. So you can remove this part:
tasks.whenTaskAdded { task ->
if(task.name == "jsLegacyBrowserTest" || task.name == "jsLegacyNodeTest") {
task.enabled = false
}
}
and it starts to work.
@InsanusMokrassar the proper fix is in progress.
In the meantime, your project doesn't seem to use js legacy target. So you can remove this part:
tasks.whenTaskAdded { task -> if(task.name == "jsLegacyBrowserTest" || task.name == "jsLegacyNodeTest") { task.enabled = false } }
and it starts to work.
Your advice working, thank you :)
Describe the bug
We've got following report in Kotlin issues where
jvmRuntimeClasspath
configuration could not be further modified as it was already resolved:The problem comes from both user repository and JB Compose Gradle plugin:
tasks.whenTaskAdded()
API here which triggers eager tasks creation.AbstractConfigureDesktopPreviewTask
task which itself triggerstryGetSkikoRuntimeIfNeeded()
method. Inside this methodpreviewClasspath
FileCollection
is resolved which prevents further configuration modification (adding new dependencies)Affected platforms
Versions
To Reproduce Steps to reproduce the behavior:
0.21.0
branch./gradlew :micro_utils.android.pickers:help -i -s
Expected behavior
Configurations should not be resolved on Gradle configuration phase.