[Commented] (WAGON-567) Wagon should retry download on server side errors

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[Commented] (WAGON-567) Wagon should retry download on server side errors

Michael Osipov (Jira)

    [ https://issues.apache.org/jira/browse/WAGON-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16947334#comment-16947334 ]

xueqian zhang commented on WAGON-567:

Raised prĀ [https://github.com/apache/maven-wagon/pull/57/files]

> 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
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
> 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