xueqian zhang created WAGON-567:
-----------------------------------
Summary: Wagon should retry download on server side errors
Key: WAGON-567
URL: https://issues.apache.org/jira/browse/WAGON-567
Project: Maven Wagon
Issue Type: New Feature
Components: wagon-http
Reporter: xueqian zhang
Currently wagon has a retry mechanism when there are connections issues with
repository manager like maven central, artifactory or nexus, see [wagon
source|[https://github.com/apache/maven-wagon/blob/dfd22586b6b934aa5a652ca32d57ed26067432fd/wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/AbstractHttpClientWagon.java#L403]]
and [httpclient
source|[https://github.com/apache/httpcomponents-client/blob/4.5.x/httpclient/src/main/java/org/apache/http/impl/execchain/RetryExec.java#L90]].
However, when the repo returns errors like 500 or 503, it does not. The 5xx
response from the repo might be a blip and maven should retry before giving up.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
