We're at 8030 kotlin libraries on MavenCentral aft...

# feed

[Big Chungus]

We're at 8030 kotlin libraries on MavenCentral after last night's kamp.petuska.dev scan! An increase of 494 since 2022-02-01 (just over a month and a half ago).
Apologies for the spam - over and out! K K

[russhwolf]

Have you considered adding more sorting or filtering options? It's really hard to discover new things with the current interface (unless they're at the beginning of the alphabet or you already know the name)

[Big Chungus]

I have. Searching by github tags, filtering by last updated daterange, providing stats page and Library page like on npm with extra data is all on the roadmap. I simply don't have the time to do it all plus my focus now is kmdc so I could rewrite kamp with compose-web and maybe even provide intellij plugin via compose-desktop.

But if you think of something else, do raise an issue on the repo so the idea would not get lost

[Big Chungus]

A "new & updated" page to showcase recent developments would probably be a good idea too.

[Big Chungus]

And after all that I'll probably look into "author claims" feature where lib authors could claim their libs on kamp and manually add extra data to make it more discoverable (categories, useful links, better descriptions, etc...)

[Albert Chang]

How are you judging whether a library is a Kotlin library?

[Big Chungus]

Via gradle metadata. This does mean that kotlin libs published via maven or older versions of gradle are not detected.

[Albert Chang]

Does it only include jar libraries?

[Big Chungus]

No, it includes all kmp combinations

[Big Chungus]

e.g. aar built with kotlin or kmp library with aar artefact. Pretty much all libs returned when filtering by android are aar artefacts

[Albert Chang]

I asked because it doesn't seem to be including my library.

[Big Chungus]

Is it published with gradle metadata?

[Big Chungus]

There's also a known bug in the scanner preventing it from detecting modules if there's already a module detected higher up the same path

[Albert Chang]

I’m not actually configuring anything related to gradle metadata but if you mean .module file, it is there.

[Big Chungus]

Hmm, could you please raise an issue on github.com/mpetuska/kamp please? Something else seems to be bugged.

[Big Chungus]

Looks like kotlin metadata is not present in your .module file. Maybe kotlin plugin in use is outdated too much?

[Albert Chang]

I’m using 1.6.10. Could it be related to gradle-maven-publish-plugin? I noticed that Google’s Accompanist which is using the same plugin is also missing from the index.

[Big Chungus]

Might be. I personally always use maven-publish and all my stuff is in the index

[andylamax]

my stuff is in the index too and I use maven-publish as well

[Albert Chang]

It actually doesn’t seem to be related to the plugin because this and this are also using the plugin and are both indexed.

[Albert Chang]

And considering the extremely low number of Android-only libs compared to multiplatform Android libs in the index, I highly suspect that there are many missing Android libs.

[Big Chungus]

Really odd, as there are tons a decent number of android-only libs already present. This certainly needs a proper look.

[Big Chungus]

I still have no clue why, but the core reason your lib is not in the index is because your .module has no mention of kotlin in variant attributes.

zoomable-1.4.1.module

[Big Chungus]

Namely "org.jetbrains.kotlin.platform.type" as seen in this android only lib from the index

adobecolortool-1.0.4.module