what is the point / use of the `metadata` artifact? I was trying to add `com.soywiz:klock` to my mul...

# multiplatform

[Dico]

what is the point / use of the metadata artifact?
I was trying to add com.soywiz:klock to my multiplatform project, and I was struggling because I couldn't find a recent version for which all artifacts are present in the maven repository.
I cloned its source and installed it to my local maven repository. The klock artifact is not present, but I tried adding klock-metadata as a dependency.
It worked in one subproject, although I didn't try compiling, but not in another.
@Deactivated User

[serebit]

metadata is the same as common

[serebit]

any multiplatform project will generate a metadata artifact along with artifacts for each target

[Dico]

good to know, thank you

[serebit]

no problem. it confused me as well, i’m surprised the kotlin team didn’t anticipate such confusion in having the standard libraries end in common and custom libraries end in metadata

[Dico]

it wouldn't hurt too much to rename it

[Dico]

I don't think

[Dico]

For the record, Android Studio has a nice little build button in the bottom left which runs gradle but doesn't refresh gradle. Well, usually not. Have to say though, it's not in your face like IntelliJ is with gradle build scripts, under the default settings at least.