[MNG-7708] Resolver in Maven 3.9+ no longer retries on a conection failure

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.9.0
• Fix Version/s: 3.9.1
• Component/s: Artifacts and Repositories
• Assignee: Tamas Cservenak
• Reporter: Jaromir Hamala
• Created: 23/Feb/23 13:14
• Updated: 14/Mar/23 13:36
• Resolved: 11/Mar/23 19:25

Description

It looks resolver in Maven 3.9+ no longer retries on a connection failure.

 

The Wagon transport configures the internal HTTP client for retries: https://github.com/apache/maven-wagon/blob/88e8574c69d83e6a658fcd2ad10f3f80926b8840/wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/AbstractHttpClientWagon.java#L560

 

The Native transport does not do that: https://github.com/apache/maven-resolver/blob/97dfd1c2b9deb15734d5e401807e55cd0498332a/maven-resolver-transport-http/src/main/java/org/eclipse/aether/transport/http/HttpTransporter.java#L190-L200

 

In environments where idle connection connections are killed, Maven 3.9+ often fails to resolve/download artefacts. A typical example is Azure Pipelines.

 

Consider exposing configuration options to re-enable retries, perhaps even retry by default as it was the case with Wagon.

Issue Links

• is fixed by: MRESOLVER-326 Resolver transport-http should retry on failures
• is fixed by: MNG-7715 Upgrade to Maven Resolver 1.9.6