Paulo Cereda
11/21/2025, 8:44 AMw: [:dokkaGeneratePublicationHtml] Couldn't resolve link for io.ktor.client.plugins.ClientRequestException in <file>/<fully qualified method>
In the KDoc, I tried
@throws io.ktor.client.plugins.ClientRequestException <description>
and
@throws ClientRequestException <description>
with no luck. It's a KMP library. Any suggestions on what's happening? First time I stumbled upon this warning, and since we enable failOnWarning, we cannot move. π Thanks!CLOVIS
11/21/2025, 8:57 AMdokkaSourceSets.configureEach {
externalDocumentationLinks.register("ktor") {
url.set(URI("<https://api.ktor.io/>"))
}
}Paulo Cereda
11/21/2025, 10:25 AMPaulo Cereda
11/21/2025, 10:25 AMPaulo Cereda
11/21/2025, 12:02 PMFlow not being resolved).
Junie tried for more than 20 minutes, and, at the end, it threw the towel by replacing @throws in the KDoc by Throws ... (plain text), so it wouldn't get processed by Dokka...Paulo Cereda
11/21/2025, 12:23 PMbuild.gradle.kts file: https://gitlab.com/islandoftex/libraries/ctan-api/-/blob/development/build.gradle.kts?ref_type=heads#L169-215Oleg Yukhnevich
11/21/2025, 12:35 PMPaulo Cereda
11/21/2025, 2:09 PMOleg Yukhnevich
11/21/2025, 2:22 PMPaulo Cereda
11/22/2025, 10:38 AMlinuxX64() as target. Good news! The warnings were reduced from 4 to one (two were from Ktor, one from coroutines). π
There's only one remaining warning, this time from an unresolved link for java.io.IOException. Now that included a native target, I noticed that our common code has some JVM-specific things, but since we were only targeting the JVM, the code worked like a charm. I will check our code and fix those inconsistences. π
That said, I think the issue is indeed related. I will dig more and see what I can find. Thanks!Oleg Yukhnevich
11/22/2025, 12:19 PM