If you use wagon http - and not lightweigh - it should have retries by default.
Le 1 déc. 2017 22:31, "Valentyn Tymofieiev" <valen...@google.com> a écrit : > Has this ever been brought up in Maven dev community? Perhaps they have > some suggestions. It sounds like a reasonable feature request. > > On Fri, Dec 1, 2017 at 1:18 PM, Kenneth Knowles <k...@google.com> wrote: > >> I've repeatedly searched around for a way to just add proper retry to >> maven or gradle, and haven't found anything :-( >> >> I had thought that we altered our builds in such a way that the .m2 >> directory was permitted to survive across builds. True that it isn't >> hermetic, precisely, but it is pretty safe to treat as a cache of immutable >> data, which is no more dangerous than having a caching incremental build >> system. >> >> Kenn >> >> On Wed, Nov 29, 2017 at 3:39 PM, Eugene Kirpichov <kirpic...@google.com> >> wrote: >> >>> Our builds often hit transient Maven network issues, e.g. this one >>> https://builds.apache.org/job/beam_PostCommit_Java_MavenInst >>> all/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? >>> >> >> >
