This is an automated email from the ASF dual-hosted git repository. kwin pushed a commit to branch feature/doc-retry-limitations-of-jetty-url-transporter in repository https://gitbox.apache.org/repos/asf/maven-resolver.git
commit 835122da44d4df4469bfc1c746914adfacb76f91 Author: Konrad Windszus <[email protected]> AuthorDate: Tue Oct 27 13:40:10 2026 +0100 Document the missing support of configurable retries in URL and Jetty Transporter --- src/site/markdown/transporter-known-issues.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/site/markdown/transporter-known-issues.md b/src/site/markdown/transporter-known-issues.md index 0ae284398..b0dc6824f 100644 --- a/src/site/markdown/transporter-known-issues.md +++ b/src/site/markdown/transporter-known-issues.md @@ -66,6 +66,7 @@ you need to add `org.apache.maven.resolver.transport:transport-http-jetty` artif This situation is probably improving with Jetty 13 (which is supposed to be shipping with a native Java QUIC implementation). * When HTTP/3 is configured there is [no fallback to lower versions](https://github.com/jetty/jetty.project/issues/15423). The request will just time out. +* Jetty currently does not support configurable retries. ## The `url` (Consumer Only) Transporter @@ -84,6 +85,7 @@ Supported features: * HTTP auth caching (lowers "known to be needed" HTTP round-trips) * Smart checksums (extracts checksums from response headers, potentially halves the HTTP round-trips) * Timeout for connection and request +* No configurable retries This transport is not a fully functional transport, and should be handled as such. It is quite usable in artifact consumption scenarios, but it is not suitable for artifact deployment.
