Don’t know if this is the right place to discuss but my Compose project is telling me to remove `jce...

# compose

[Sam]

Don’t know if this is the right place to discuss but my Compose project is telling me to remove jcenter but when i do, all hell breaks loose and i can no longer compile

[Shivam Sethi]

same here it will not build if I remove which is what its telling me to

[Sam]

yep it complains about dozens of dependencies, most of which aren’t even directly referenced in our project

[Filip Wiesner]

It's just a suggestion and warning for the future because jcenter will stop working at the end of the year (if I remember correctly). It does not mean that you have to remove it right now.

[erickuck]

Looks like you aren't using mavenCentral at all. That’s the replacement for jcenter

[Sam]

@erickuck so just replace jcenter() with mavenCentral() and roll the dice?

[erickuck]

Not much of a dice roll but sure

[Filip Wiesner]

Not all jcenter dependencies are ported to mavencentral. And not all will ever be. If it works for you, fine. But it won't work for everyone.

[erickuck]

That’s something you need to figure out then. Jcenter is going away so you can't just ignore it

[Sam]

even though the dice weren’t suppose to exist, i rolled them anyway and:

[ephemient]

https://github.com/google/ExoPlayer/issues/5246 https://github.com/Kotlin/kotlinx.collections.immutable/issues/96 etc.

[Sam]

thanks @ephemient for the reference

[ephemient]

for all dependencies currently on jcenter, you need to find replacements - hopefully the same library published on mavenCentral - within the next year. do your own research

[Sam]

feels like org.rekotlin com.google.android and org.jetbrains.kotlinx libs shouldn’t be the type of libs giving problems but here we are

[ephemient]

the jcenter shutdown caught everybody by surprise, there's a big thread in #feed

[ephemient]

https://kotlinlang.slack.com/archives/C0BJ0GTE2/p1612372634063700

[Sam]

soo is the tl;dr here that we cannot remove jcenter until everyone isnt surprised anymore?

[Filip Wiesner]

It's not a problem just yet. You can still use jcenter. Just be ready to migrate and be careful when adopting libraries that haven't migrated yet

[ephemient]

or... nobody is still maintaining your dependency, and you have to find a replacement

[ephemient]

but the timeline has been extended, so it's just a warning for the next year

[ephemient]

as a consumer of the dependency, anyway. if you're publishing packages you need to be migrating sooner than that

[Sam]

yep im looking at org.rekotlin it’s the only lib in our codebase that will give us problems in the long run

[eygraber]

Also the 3 month timeline is for new deploys. They'll be serving packages until February 2022 I believe

[Colton Idle]

Nothing to do with compose, but maybe the latest versions of AGP/AS have started warning about this.

https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

You still have a year or so to migrate.

[arkon]

You should reach out to library owners to make sure they’re aware of it too.

[Sam]

@arkon already on it: https://github.com/ReKotlin/ReKotlin/issues/47