[GitHub] maven-wagon issue #37: making the retry handle of http client configurable

Github user jkff commented on the issue: https://github.com/apache/maven-wagon/pull/37 Wait: the default one would give current behavior, which doesn't retry on socket errors. Did you mean `-Dmaven.wagon.http.retryhandler.class=standard` perhaps, and without the `nonRetryableCl

[GitHub] maven-wagon issue #37: making the retry handle of http client configurable

Github user jkff commented on the issue: https://github.com/apache/maven-wagon/pull/37 I see. So, for example, what's the shortest way to configure this to simply retry everything, including socket exceptions, host resolution exceptions etc? (what we want in Beam builds

[GitHub] maven-wagon issue #37: making the retry handle of http client configurable

Github user jkff commented on the issue: https://github.com/apache/maven-wagon/pull/37 Very nice! Could you comment more on how to use this in practice to improve reliability w.r.t. common network issues? Is the default behavior changed