Trying to run an app that isn't mine. I get this e...
# random
c
Trying to run an app that isn't mine. I get this error. Is this just due to the fact that bintray was shutdown, or is this actually an intermittent issue that should resolve itself at somepoint soon? Could not HEAD 'https://jcenter.bintray.com/org/jetbrains/dokka/org.jetbrains.dokka.gradle.plugin/1.4.32/org.jetbrains.dokka.gradle.plugin-1.4.32.jar'. Received status code 502 from server: Bad Gateway
plus1 2
n
glad i’m not the only one
i dunno how to work right now 🤷‍♀️
p
seems to be an actual outage
🙏 1
n
i removed all references of jcenter and bintray from my project but it’s still not not building
i
plugin portal is experiencing partial outage, JCenter downloads specifically https://status.gradle.com/. Hopefully, it's all related, they'll fix it and it goes back to normal, but who knows
n
what should we do instead of work now?
starcraft or go outside?!
👀 2
c
outside?
n
someone suggested that before but i’m not really sure what it is?
m
Maybe it was 'Planetside'
i
you can always watch the Book of Boba Fett on Disney+ 😉
c
Disney+ is down. It too somehow runs on jcenter. 🧌
😄 3
e
try putting
mavenCentral()
before
gradlePluginPortal()
so that it is searched first
c
mavenCentral is in front of gPP in this repo (been trying to run this repo since the morning) still no luck. lol
n
heh yeah still no luck either.
e
😞
somehow whatever versions we're on seem to work, but we're not using Dokka
n
There was an issue with the resolution of
maven-metadata.xml
and also jCenter is down
i
However regular library dependencies of plugins will still fail to resolve because of the underlying failure of JCenter.
sad
m
glad i’m not the only one experiencing this issue 😞
k
Glad I'm not the only one! Has anyone found a solution for this yet?
c
Came across this
Copy code
repositories {
        gradlePluginPortal() {
            metadataSources {
                ignoreGradleMetadataRedirection()
            }
        }
        ...
    }
and it seems to have worked for me
e
according to Gradle status, everything should be working now, unless the plugins you use have library dependencies that were never mirrored outside of JCenter
n
@Colton Idle you shouldn’t need this workaround as the metadata issue is resolved
k
How about jnunit 4?
c
everything is good to go. hooray