The jdk (Java HttpClient) Transporter

Given this transporter uses the Java HttpClient (available since Java 11), it is the user's best interest to use latest patch version of Java, as HttpClient is getting bugfixes regularly.

Known issues:

• Does not properly support aether.transport.http.requestTimeout configuration prior Java 26, see JDK-8208693
• No TLS Proxy support, see here
• No SOCKS proxy support, see JDK-8214516
• In case of Proxy TLS tunneling, to enable Proxy Basic authentication, one must use jdk.http.auth.tunneling.disabledScheme Java System Property, see here. Java versions since 8u111 have this property set to value “Basic” making HTTP Basic authentication disabled, see here. To enable HTTP Basic authentication for Proxy TLS tunneling, one must set jdk.http.auth.tunneling.disabledScheme to empty string, e.g. by adding -Djdk.http.auth.tunneling.disabledScheme="" JVM argument.

Maven 4 uses this transport by default for HTTP(S) protocol.

The apache (Apache HttpClient) Transporter

Transporter based on Apache HttpClient.

To use this transporter in Maven 4, you need to specify -Dmaven.resolver.transport=apache user property.

The jetty (Jetty HttpClient) Transporter

Transporter based on Jetty HttpClient.

In Maven 4 this transport is not available by default (is not bundled). To use it, you need to add org.apache.maven.resolver.transport:transport-http-jetty artifact with its runtime dependencies to /lib directory of Maven. Once added to core classpath, it will take over the role of default transport.