Re: Received status code 500 from server: Internal Server Error

2019-10-08 Thread jincheng sun
Thanks for your quick response, I think your approach is work locally. Thank you! @ Łukasz I seed this info to dev ML not for my local env. But for all the Beam Contributors, because they will got the PreCommit fail when open the PR. Anyway, Thanks for your kind solution for locally. Currently, I

Re: Received status code 500 from server: Internal Server Error

2019-10-08 Thread Kyle Weaver
Is there a way we could add a backup server url to our configuration to use if the sonatype server is down? On Tue, Oct 8, 2019 at 4:56 AM Łukasz Gajowy wrote: > of course I meant: > > maven { url "https://oss.sonatype.org/content/repositories/staging/; } > => maven { url

Re: Received status code 500 from server: Internal Server Error

2019-10-08 Thread Łukasz Gajowy
of course I meant: maven { url "https://oss.sonatype.org/content/repositories/staging/; } => maven { url "https://repo1.maven.org/maven2/; } :) wt., 8 paź 2019 o 13:53 Łukasz Gajowy napisał(a): > It seems that oss.sonatype was down and this prevented us from downloading > required resources

Re: Received status code 500 from server: Internal Server Error

2019-10-08 Thread Łukasz Gajowy
It seems that oss.sonatype was down and this prevented us from downloading required resources from it. I can't use it either (I was getting the same error). If running gradle in offline mode does not help (--offline flag) another temporary solution is to replace the url In Repository.groovy