This is an automated email from the ASF dual-hosted git repository.
kwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-resolver.git
The following commit(s) were added to refs/heads/master by this push:
new a78c1b35b Document the missing support of configurable retries in URL
and Jetty (#2237)
a78c1b35b is described below
commit a78c1b35b530dcb592d9f513cc6068ec2de656e8
Author: Konrad Windszus <[email protected]>
AuthorDate: Wed Oct 28 09:58:35 2026 +0100
Document the missing support of configurable retries in URL and Jetty
(#2237)
---------
Co-authored-by: Guillaume Nodet - AI Bot <[email protected]>
---
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..a6173b5bb 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.
+* Does not support configurable retries.
## The `url` (Consumer Only) Transporter
@@ -93,3 +94,4 @@ artifact consumption scenarios, but it is not suitable for
artifact deployment.
* Does neither support HTTP/2 nor HTTP/3
* Supports only GET/HEAD, usable only for artifact consumption
* Is and will never be present in Maven; is meant for applications integrating
Resolver
+* Does not support configurable retries.
