hi folks - fyi that jetbrains uploaded a new, JDK ...

# dokka

[Zac Sweers]

hi folks - fyi that jetbrains uploaded a new, JDK 11-only version of org.jetbrains:markdown (which dokka depends on) to maven central yesterday with the same version that's on jcenter. If you haven't set up your repo to only source it from jcenter, your builds will almost certainly break imminently if you don't have a cached version of the dep local. Easy way to test is ./gradlew help --refresh-dependencies

[Lukas K-G]

It just broke for me. 🤦 Thanks for the insights.

[mkrussel]

Is there a way to fix this?

[Lukas K-G]

I was lucky and we were able to just ditch maven central. Not sure if there is a different way. 🤔

[Lukas K-G]

Maybe something like https://docs.gradle.org/5.1.1/release-notes.html#repository-to-dependency-matching might help.

[Lukas K-G]

Or even this link:
https://docs.gradle.org/5.1.1/userguide/declaring_repositories.html#sec::matching_repositories_to_dependencies

[Zac Sweers]

What Lukas said is the right approach, but we've had issues with that in kotlin dsl

[Zac Sweers]

an easy but unfortunate last resort is to move jcenter ahead of central until a fixed version is released

[mkrussel]

So this fixed it for me. Tried it before, but forget to add to the plugins repositories section.

mavenCentral {
            content {
                excludeModule("org.jetbrains", "markdown")
            }
        }

[mkrussel]

Since I'm trying to get off of jcenter and on to mavenCentral, removing mavenCentral didn't make sense.

[Kamil Doległo]

I has been fixed, you’ll have to clean the caches manually I believe: https://github.com/JetBrains/markdown/issues/70

[Zac Sweers]

cleaning caches has not resolved this in my experience

[Zac Sweers]

I think they need to release a new 0.1.46 copy instead of trying to trick package managers

[Zac Sweers]

looks like that's what they just did 👍