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

Herve Boutemy commented on WAGON-567:
-------------------------------------

[~michael-o] just had a look at this commit
Can you confirm that by default (= no configuration anywhere, like in Maven 
core by default), no new retry will be added vs the previous behaviour?
then IIUC, additionnal behaviour (for those who know...) can be configured via 
system properties (names can be found in code)

I'm confused:
1. between "none" vs "default" vs "standard" names of the predefined strategies
2. and the default choice that looks to be "none"

> Provide request retry strategy on transient client and 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
>            Assignee: Michael Osipov
>            Priority: Minor
>             Fix For: 3.3.4
>
>          Time Spent: 20m
>  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#L393]
>  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],
>  [httpclient default retry 
> handler|https://github.com/apache/httpcomponents-client/blob/4.5.x/httpclient/src/main/java/org/apache/http/impl/client/DefaultHttpRequestRetryHandler.java#L154].
>  However,  it only captures low level connection issues. When the repo 
> returns errors like 500 or 503, it does not retry. 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)

Reply via email to