-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolution of platform dependencies fails the build with Kotlin 1.9 / Gradle 8 #3153
Comments
The first property appears to have worked for Redwood. Thanks! I did not try the others. |
Adds a workaround for running Dokka with Gradle 8 and Kotlin 1.9.0; otherwise it leads to build errors related to platform dependency resolution For more details, see Kotlin/dokka#3153
The first property resolved the issue in my library as well. Thank you! By the way, I believe you meant "try them in descending order". |
Adds a workaround for running Dokka with Gradle 8 and Kotlin 1.9.0; otherwise it leads to build errors related to platform dependency resolution For more details, see Kotlin/dokka#3153
The first property worked for me too as a workaround. I was struggling very hard before finding this issue :( |
Adds a workaround for running Dokka with Gradle 8 and Kotlin 1.9.0; otherwise it leads to build errors related to platform dependency resolution For more details, see Kotlin/dokka#3153
This problem was fixed in Dokka 1.9.10, so it no longer requires the flags mentioned above.
Thanks to everyone who tested the solution and provided feedback! I'll close the issue now as we haven't seen any new reports about it recently, so hopefully it's all working as expected |
Hi @IgnatBeresnev, A problem was found with the configuration of task ':detox:dokkaJavadoc' (type 'DokkaTask').
Here is the branch: https://github.com/wix/Detox/tree/5a63be0ce84ca17068a394b241d472968f61c1e7
Non of the workaround worked for me. |
Important
This issue was fixed in Dokka 1.9.10, so if you update to it, it should be gone. No additional flags are required in Dokka 1.9.10.
Problem
Due to a combination of reasons, Gradle builds might fail with one of the following problems:
or
Cause
It's difficult to pinpoint the exact reason for these errors as multiple factors contribute to it:
implementationMetadataConfiguration
in KGP)cinterop
kotlin.mpp.enableCInteropCommonization
being set totrue
includeBuild
Depending on the combination, it will lead to one of the mentioned errors.
Workarounds
Unfortunately, the potential fixes were found late into testing Dokka 1.9.0. We did not want to make rushed decisions that could break unaffected projects, but we also did not want to delay the release even more, so we settled on providing workarounds in Dokka 1.9.0 that are disabled by default.
Important
This issue was fixed in Dokka 1.9.10, so if you update to it, it should be gone. No additional flags are required in Dokka 1.9.10.
There are three flags that change the way Dokka resolves platform dependencies. The flags are mutually exclusive, please try them in descending order (from top to bottom):
org.jetbrains.dokka.classpath.useNativeDistributionAccessor=true
org.jetbrains.dokka.classpath.useKonanDistribution=true
org.jetbrains.dokka.classpath.excludePlatformDependencyFiles=true
- last resort, ignores platform dependencies altogether, so you might seeError class
in signatures.You can add these flags to your
gradle.properties
or pass them as a project property in CLI:Please, let us know if any of these workarounds (or especially all of them) didn't help.
Short-term solution
We aim to ship a well-tested solution that will be enabled by default in Dokka 1.9.10, likely some time in October.
Long-term solution
We're taking the necessary steps to resolve this problem for good (#3121) and to discover similar compatibility problems very much in advance, before our users experience them. We plan to implement it by Kotlin 2.0 / 2.1, but no later than the first Stable release of Dokka.
The text was updated successfully, but these errors were encountered: