We re at 8030 kotlin libraries on MavenCentral after last ni

Question

We re at 8030 kotlin libraries on MavenCentral after last night s <http kamp petuska dev|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 kotlin intensifies kotlin intensifies purple

russhwolf · Answer

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 · Answer

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 · Answer

A new amp updated page to showcase recent developments would probably be a good idea too

Big Chungus · Answer

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 · Answer

How are you judging whether a library is a Kotlin library

Big Chungus · Answer

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

Albert Chang · Answer

Does it only include jar libraries

Big Chungus · Answer

No it includes all kmp combinations

Big Chungus · Answer

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 · Answer

I asked because it doesn t seem to be including <https search maven org artifact com mxalbert zoomable zoomable|my library>

Big Chungus · Answer

Is it published with gradle metadata

Big Chungus · Answer

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 · Answer

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

Big Chungus · Answer

Hmm could you please raise an issue on <http github com mpetuska kamp|github com mpetuska kamp> please Something else seems to be bugged

Big Chungus · Answer

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

Albert Chang · Answer

I m using 1 6 10 Could it be related to <https github com vanniktech gradle maven publish plugin|gradle maven publish plugin> I noticed that Google s Accompanist which is using the same plugin is also missing from the index

Big Chungus · Answer

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

andylamax · Answer

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

Albert Chang · Answer

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

Albert Chang · Answer

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 · Answer

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

Big Chungus · Answer

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

Big Chungus · Answer

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