[WAGON-567] Provide request retry strategy on transient client and server side errors

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.3.4
• Component/s: wagon-http
• Assignee: Michael Osipov
• Reporter: xueqian zhang
• Created: 09/Oct/19 03:11
• Updated: 08/Nov/19 09:08
• Resolved: 29/Oct/19 21:27

Description

Currently wagon has a retry mechanism when there are connections issues with repository manager like maven central, artifactory or nexus, see wagon source and httpclient source, httpclient default retry handler. 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.

Issue Links

• links to: GitHub Pull Request #57