Document known transport issues#1792
Conversation
|
|
||
| ## The `apache`, Apache HttpClient Transport | ||
|
|
||
| To use this transport, you need to specify `-Dmaven.resolver.transport=apache` user property. |
There was a problem hiding this comment.
Please mention that Maven 3.x only ships with this transport, therefore the other transports cannot be used and this one doesn't need to be enabled explicitly.
There was a problem hiding this comment.
This is site for Resolver 2.x, Maven 3 uses Resolver 1.x. Do we really want to mix things here?
I'd rather add a link on index page "if you use Maven 3 go here..."
There was a problem hiding this comment.
Also fine, but this is the default documentation if one goes to https://maven.apache.org/resolver/. Most people will not be aware which version is used in which Maven.
| Known issues: | ||
| * Does not properly support `aether.transport.http.requestTimeout` prior Java 26, see [JDK-8208693](https://bugs.openjdk.org/browse/JDK-8208693) | ||
| * No TLS proxy support, see [here](https://dev.to/kdrakon/httpclient-can-t-connect-to-a-tls-proxy-118a) | ||
| * In case of Proxy TLS tunneling, to enable Proxy authentication one must issue `jdk.http.auth.tunneling.disabledSchemes`, see [here](https://docs.oracle.com/en/java/javase/21/core/java-networking.html#GUID-801380C1-4300-4ED8-A390-3C39135267CD). |
There was a problem hiding this comment.
Please mention that most JREs have this default value Basic (I checked Temurin 11, 17, 21, 25). Was introduced in 8u111 (https://www.oracle.com/java/technologies/javase/8u111-relnotes.html) for security reasons.
|
Maybe we can documents known issues on Maven site page, eg like we have: https://maven.apache.org/guides/mini/guide-resolver-transport.html it can be easier add new issues, or edit independent of revolver release |
| @@ -0,0 +1,45 @@ | |||
| # Transport Known Issues | |||
There was a problem hiding this comment.
I find the naming "Transporter" more intuitive for these things. Transport is a single request/response cycle for me.
|
|
||
| This page lists known issues related to various transports. | ||
|
|
||
| ## The `jdk`, JDK Transport |
There was a problem hiding this comment.
| ## The `jdk`, JDK Transport | |
| ## The `jdk`, JDK HttpClient Transport |
|
|
||
| ## The `jdk`, JDK Transport | ||
|
|
||
| This is the default transport used in Maven 4. Given this transport uses the Java, it is in user best interest |
There was a problem hiding this comment.
| This is the default transport used in Maven 4. Given this transport uses the Java, it is in user best interest | |
| This is the default transport for http(s) protocol used in Maven 4. Given this transport uses the Java, it is in user best interest |
|
|
||
| ## The `jetty`, Jetty HttpClient Transport | ||
|
|
||
| This transport is not available by default (is not bundled with Maven). To use it, |
There was a problem hiding this comment.
| This transport is not available by default (is not bundled with Maven). To use it, | |
| This transport is not available by default (is not bundled with any Maven version). To use it, |
Let us rather link from a Maven page to this one. The transport limitations listed here are not Maven specific! |
This is resolver, that is used in Maven.
|
|
||
| Transporter based on Apache HttpClient. | ||
|
|
||
| To use this transporter in Maven 4, you need to specify `-Dmaven.resolver.transport=apache` user property. |
There was a problem hiding this comment.
I think this also lacks SOCKS Proxy support...
Co-authored-by: Konrad Windszus <[email protected]>
Co-authored-by: Konrad Windszus <[email protected]>
Co-authored-by: Konrad Windszus <[email protected]>
Co-authored-by: Konrad Windszus <[email protected]>
Co-authored-by: Konrad Windszus <[email protected]>
|
|
||
| ## The `jdk` (Java HttpClient) Transporter | ||
|
|
||
| Given this transporter uses the Java HttpClient (available since Java 11), it is in user best interest |
cstamas
added
documentation
4 participants
Document "known issues" for transports, for start the HTTP capable transports.