Hi, why we can't find my library on klibs <https:/...
# klibs-io
u
Hi, why we can't find my library on klibs https://github.com/kdroidFilter/ComposeNativeTray (
p
Hi, I created a ticket to review why library was not added. You can find it here: https://github.com/klibs-io/issue-management/issues/43
u
Thanks a lot !
👍 1
m
Most libraries aren't on because klibs currently uses search.maven.org which is known to have indexing issues.
d
@אליהו הדס, I'd like to duplicate the answer from the issue here and close it. The rules for showing libraries on klibs.io are described here: https://klibs.io/faq Unfortunately, For the ComposeNativeTray packages, there is no published
*-kotlin-tooling-metadata.json
file, that is why your library is not presented in klibs.io.
u
@Dmitrii Krasnov Thank you very much, but how do I add a -kotlin-tooling-metadata.json in my lib ?
d
It is a good question.
kotlin-tooling-metadata.json
file should be published by default if you use the standard
maven-publish
plugin. (More information about publishing Kotlin multiplatform libraries can be found here) From a quick search in your repo, I see that you use
com.vanniktech.maven.publish
for publishing, and I expect that is the reason.
u
No, I'm using also the vanniktech plugin for this lib https://klibs.io/project/kdroidFilter/ComposeMediaPlayer
d
Oh, I see now, https://github.com/kdroidFilter/ComposeNativeTray is not a multiplatform project. You use
kotlin("jvm") version "2.1.20"
there. But klibs.io now is showing only
multiplatform
libraries like: https://klibs.io/project/kdroidFilter/ComposeMediaPlayer
u
ah ok, thank you very much. that is to say that if I apply the kmp plugin, and only target the jvm, is it ok?
d
> ah ok, thank you very much. that is to say that if I apply the kmp plugin, and only target the jvm, is it ok? I expect that it will also require slightly changing the source set hierarchy, but it should generally work then.
👍 1
u
🆒 1
👍 1