[
https://issues.apache.org/jira/browse/MNG-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-7708:
---------------------------------
Component/s: Artifacts and Repositories
> Resolver in Maven 3.9+ no longer retries on a conection failure
> ---------------------------------------------------------------
>
> Key: MNG-7708
> URL: https://issues.apache.org/jira/browse/MNG-7708
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.9.0
> Reporter: Jaromir Hamala
> Assignee: Tamas Cservenak
> Priority: Minor
> Fix For: 3.9.1
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
