Thread
#compose
    s

    Sam

    1 year ago
    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
    s

    Shivam Sethi

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

    Sam

    1 year ago
    yep it complains about dozens of dependencies, most of which aren’t even directly referenced in our project
    Filip Wiesner

    Filip Wiesner

    1 year ago
    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.
    e

    erickuck

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

    Sam

    1 year ago
    @erickuck so just replace
    jcenter()
    with
    mavenCentral()
    and roll the dice?
    e

    erickuck

    1 year ago
    Not much of a dice roll but sure
    Filip Wiesner

    Filip Wiesner

    1 year ago
    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.
    e

    erickuck

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

    Sam

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

    Sam

    1 year ago
    thanks @ephemient for the reference
    e

    ephemient

    1 year ago
    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
    s

    Sam

    1 year ago
    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
    e

    ephemient

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

    Sam

    1 year ago
    soo is the tl;dr here that we cannot remove
    jcenter
    until everyone isnt surprised anymore?
    Filip Wiesner

    Filip Wiesner

    1 year ago
    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
    e

    ephemient

    1 year ago
    or... nobody is still maintaining your dependency, and you have to find a replacement
    but the timeline has been extended, so it's just a warning for the next year
    as a consumer of the dependency, anyway. if you're publishing packages you need to be migrating sooner than that
    s

    Sam

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

    eygraber

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

    Colton Idle

    1 year ago
    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

    arkon

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

    Sam

    1 year ago