Aaand we're past 4.5k kotlin libs on maven central...
# feed
b
Aaand we're past 4.5k kotlin libs on maven central! Check them out on kamp.petuska.dev
K 29
z
Is this content all automatically generated? For example, searching for “chat” surfaces one of our Stream Chat libs as seen in the screenshot below But we have several artifacts on MavenCentral https://search.maven.org/search?q=stream%20chat
Ah, the
core
artifact is the only pure Kotlin one we have, so it’s probably that Android libraries are excluded
b
It scans mavenCentral nightly to self-update. Inclusion condition is that the artefact has gradle-metadata published with kotlin attributes. So if your module uses kotlin plugin (even if there's no kotlin source files) it'll be picked up.
e
do you have a history of how many there were, say, in the last month?
would love to see some charts 😀
b
Yeah, probably should've started capturing some data snapshots a while ago 😀
z
Both of these modules have Kotlin in them and Gradle metadata published, but only the first of them show up on this site: https://repo1.maven.org/maven2/io/getstream/stream-chat-android-core/4.11.0/ https://repo1.maven.org/maven2/io/getstream/stream-chat-android-client/4.11.0/ To be fair, the latter only has Kotlin mentions in the dependencies. I think that might be the case for all Android libraries or AARs though. Might be a good idea to also include those.
b
Does the other one have kotlin plugin applied?
b
@zsmb looks like kotlin-android plugin does not add any kotlin attributes to gradle metadata, that's why it's not getting picked up.
l
@Big Chungus A fallback approach for Android libraries would be checking for an
.aar
file to exist, and check in the
pom.xml
that there's a dependency on one of the Kotlin stdlib artifacts.
b
Hmm, an interesting suggestion. I'll give it a go for the next release.