HN Explorer

9 comments

[ 4.4 ms ] story [ 33.9 ms ] thread
kulor
"502 Bad Gateway". Breaking a lot of dependencies in our Java build process.
wtf_is_up
Same here. CI pipeline failing with 502.
ColinWright
I have no idea what "bintray" is, so I did a search.

Is this relevant?

> JFrog has announced that they are shutting down the Bintray hosting service, which includes the popular JCenter hosting service for Java artifacts, as well as GoCenter (which hosted Go packages) and ChartCenter (which hosted Helm charts).

https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-clo...

This link : https://www.bintray.com

Redirects here : https://jfrog.com/distribution/?bintrayRD=1

toomuchtodo
> To clarify, the JCenter repository will keep serving packages for 12 months until February 1st 2022. Only the JCenter REST API and UI will be sunsetted on May 1st 2021.
joshuanapoli
It's blocking our React Native builds... is there any work-around?
tapvt
If you're using Gradle + jcenter repository, it will fail.

I ran into this when building a Flutter mobile app, relying on Gradle to fetch dependencies.

There is more information here: https://blog.gradle.org/jcenter-shutdown

I was able to find all the dependencies I needed on the Maven Central repository, so it was a quick fix in my case.

kulor
Same, I've been banging my head against this issue for half of today and no resolve yet (ironically ran into this after I fixed a slew of unrelated iOS build issues). My issue is with sub dependency reliance on jcenter (e.g react-native-pdf). Given Java/Gradle isn't my domain of expertise, I can't yet find a clean way of intercepting bintray requests and subbing them out for Maven/Google hosted equivalents (which seem to exist).

I don't hold out much hope that JFrog will expedite a fix for this given their intention to phase out of service.