Our builds often hit transient Maven network issues, e.g. this one https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/5331/consoleFull
2017-11-29T02:18:02.936 [ERROR] Failed to execute goal on project beam-sdks-java-io-hadoop-jdk1.8-tests: Could not resolve dependencies for project org.apache.beam:beam-sdks-java-io-hadoop-jdk1.8-tests:jar:2.3.0-SNAPSHOT: Could not transfer artifact org.apache.derby:derby:jar:10.10.2.0 from/to central (https://repo.maven.apache.org/maven2): GET request of: org/apache/derby/derby/10.10.2.0/derby-10.10.2.0.jar from central failed: Connection reset -> [Help 1] It'd be good to increase reliability of our builds. repo.maven.apache.org seems quite unreliable. I tried finding a way to configure Maven to retry such network errors and it appears to be impossible [will be happy if someone proves me wrong]. Would this issue be resolved if we used multiple mirrors? https://maven.apache.org/guides/mini/guide-mirror-settings.html Any other suggestions?
