Skip to content
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

Dokka with Kotlin 1.6.20-RC2 can't resolve dependency: Error class #2411

Closed
hfhbd opened this issue Mar 29, 2022 · 2 comments · Fixed by #2431 or #2441
Closed

Dokka with Kotlin 1.6.20-RC2 can't resolve dependency: Error class #2411

hfhbd opened this issue Mar 29, 2022 · 2 comments · Fixed by #2431 or #2441
Labels

Comments

@hfhbd
Copy link
Contributor

hfhbd commented Mar 29, 2022

Describe the bug
I use Kotlin 1.6.20-RC2 with multiplatform and a common dependency.

Expected behaviour
Documentation referencing the external class from the dependency is resolved

Screenshots
Bildschirmfoto 2022-03-29 um 19 39 40

To Reproduce
untitled1.zip

Dokka configuration

plugins {
    kotlin("multiplatform") version "1.6.20-RC2"
    id("org.jetbrains.dokka") version "1.6.10"
}

repositories {
    mavenCentral()
}

kotlin {
    js(IR) {
        browser()
    }
    jvm()

    sourceSets {
        commonMain {
            dependencies {
                // 0.0.12 uses Kotlin 1.5.30, 0.0.13-RC uses 1.6.20-RC2
                implementation("app.softwork:kotlinx-uuid-core:0.0.13-RC")
            }
        }
    }
}

Installation

  • Operating system: macOS 12
  • Build tool: Gradle v7.4.1
  • Dokka version: 1.6.10

Additional context
Using Kotlin 1.6.10 works

Are you willing to provide a PR?
Sure, but I don't know if this is a Dokka or Kotlin bug

@hfhbd hfhbd added the bug label Mar 29, 2022
@hfhbd hfhbd changed the title Dokka with Kotlin 1.6.20-RC2 can't resolve external JS types Dokka with Kotlin 1.6.20-RC2 can't resolve dependency: Error class Mar 29, 2022
@IgnatBeresnev
Copy link
Member

Hi! This is indeed a problem, most likely due to compatibility between KMP and dokka, thanks for reporting it! We'll do our best to get it fixed in 1.6.20

@vmishenev vmishenev reopened this Apr 11, 2022
@vmishenev vmishenev linked a pull request Apr 15, 2022 that will close this issue
@IgnatBeresnev
Copy link
Member

Will be released in 1.6.21 soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants