Why JB decided to publish `kotlin-wrappers` artifacts to JB Space and not to Maven Central?

# react

[Robert Jaros]

Why JB decided to publish kotlin-wrappers artifacts to JB Space and not to Maven Central?

[turansky]

cc @Sebastian Aigner

[Sebastian Aigner]

AFAIK we just wanted to make an alternative to jcenter available as quickly as possible, and since we have this infrastructure available for EAPs & Co. anyway on kotlin.jetbrains.space, it was used. Would you prefer if the library was published on MC? (and if so, could you explain your reasoning)? I’m happy to forward that.

[Sebastian Aigner]

(also cc @Leonid Khachaturov)

[Robert Jaros]

All KVision users using react or redux modules will need to add new repository location. Otherwise their builds will fail. Introducing this "breaking" change ruins my semantic versioning for KVision 😉

[turansky]

Would you prefer if the library was published on MC?

Yes, because
1. MC contains most JB libs (stdlib, coroutines, serialization…)
2. MC proxy already exists in companies, which use Kotlin
3. Space repo have open questions, like this

[Robert Jaros]

@Sebastian Aigner and you promised 🙂
https://kotlinlang.slack.com/archives/C0B8L3U69/p1613135036367600?thread_ts=1613132355.366500&cid=C0B8L3U69

[Sebastian Aigner]

Fair, and you’re raising good points, thanks for holding us accountable 😄. I’ll bring this up internally.

[Big Chungus]

Or you can quickly delete your previous message and act like it never happened 😀 Gotta move fast, though!

[Sebastian Aigner]

Upd, we’re gonna move the wrappers to Maven Central. It’s still going to take a bit, so sit tight, but they’re getting there. 🙂