`pprint-kotlin-core` publication seems broken

[Kantis]

Following the setup guide and adding

dependencies {
   implementation("io.exoquery:pprint-kotlin:2.0.0")
}

results in broken classpath

---

I believe this is caused by pprint-kotlin-core being a KMP module, which only publishes variant metadata in the "root module" pprint-kotlin-core. Consumers are supposed to be variant-aware, but I'm guessing something goes wrong due to pprint-kotlin being a JVM-only module which perhaps doesn't pull along the correct dependency.

For instance, if you look at my dependency graph you can see that other multiplatform dependencies pull along their jvm variants

[Kantis]

Seems to be broken when trying to use io.exoquery:pprint-kotlin-kmp as well

[deusaquilus]

Should be fixed in v2.0.2. Could you please try it out?

[Kantis]

Both the KMP and JVM artifacts seem fine now. Thanks!

[raamcosta]

I still cannot import pprint function from jvm module correctly with 2.0.2.

Adding the dependency to io.exoquery:pprint-kotlin:2.0.2 doesn't seem to do anything for me, I still can't import io.exoquery package.

If I change version to 1.1.0 or use -kmp dependency, it works, but with kmp version I have to use kotlinx serialization which I don't want to do. Since it's a JVM only module, I'd rather just use reflection.