When adding dependency information for using a mul...

# multiplatform

[pajatopmr]

When adding dependency information for using a multiplatform library, the platform targets are pretty obvious, e.g. implementation "<http://com.pajato.io:KFile-jvm:0.0.1|com.pajato.io:KFile-jvm:0.0.1>" or implementation "<http://com.pajato.io:KFile-native:0.0.1|com.pajato.io:KFile-native:0.0.1>" but how should common dependencies be written: implementation "<http://com.pajato.io:KFile:0.0.1|com.pajato.io:KFile:0.0.1>" or implementation "<http://com.pajato.io:KFile-metadata:0.0.1|com.pajato.io:KFile-metadata:0.0.1>"?

[pajatopmr]

I tried both and each seems to work but I’m guessing that there is a clear preference by design.

[coletz]

afaik common dependencies has the -common suffix

[coletz]

for example: org.jetbrains.kotlin:kotlin-stdlib-common, org.jetbrains.kotlinx:kotlinx-coroutines-core-common

[pajatopmr]

Hmmm. That’s interesting. I used maven-publish to get the four artifacts I see on Maven Central, one with no suffix and the other three having -metadata, -jvm and -native suffixes. Perhaps a JB or Gradle guru might comment. @olonho

[serebit]

If I’m not mistaken, the KFile dependency auto-populates the other platform dependencies if GRADLE_METADATA is enabled. If specifying platform dependencies manually, then you should use the -metadata artifact instead.