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 <[email protected]> napisał(a):
> 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
> <https://github.com/apache/beam/blob/85c0e8364376f19f2e0eb5b5c7bea6639702725b/buildSrc/src/main/groovy/org/apache/beam/gradle/Repositories.groovy#L50>
> to
> e.g. a maven central one when working locally:
>
> maven { url "https://repo1.maven.org/maven2/"; } => maven { url "
> https://oss.sonatype.org/content/repositories/staging/"; }
>
> When sonatype is up again you should be fine without this hack.
>
> I hope this helps.
>
> Łukasz
>
> wt., 8 paź 2019 o 11:55 jincheng sun <[email protected]>
> napisał(a):
>
>> Hi all,
>> I got the 500 error, when do the PreCommit. We can run the following
>> command to see the detail:
>>
>> ./gradlew :sdks:python:test-suites:portable:py2:flinkValidatesRunner
>>
>> >>
>> Task :model:pipeline:compileJava FAILED
>> FAILURE: Build failed with an exception.
>> * What went wrong:
>> Execution failed for task ':model:pipeline:compileJava'.
>> > Could not resolve all files for configuration
>> ':model:pipeline:errorprone'.
>> > Could not resolve
>> com.google.errorprone:error_prone_core:latest.release.
>> Required by:
>> project :model:pipeline
>> > Failed to list versions for
>> com.google.errorprone:error_prone_core.
>> > Unable to load Maven meta-data from
>> https://oss.sonatype.org/content/repositories/staging/com/google/errorprone/error_prone_core/maven-metadata.xml
>> .
>> > Could not HEAD '
>> https://oss.sonatype.org/content/repositories/staging/com/google/errorprone/error_prone_core/maven-metadata.xml'.
>> Received status code 500 from server: Internal Server Error
>>
>> I appreciate if anyone help solve the server problem！
>>
>> Best,
>> Jincheng
>>
>>
>>
>>
