Tamas Cservenak opened MNG-7454 and commented
We should include maven-resolver-transport-http (along with existing maven-resolver-transport-wagon) but retain Wagon as default transport, while offer ability for users to use http transport to utilize new resolver features like "smart checksums".
On positive side, this will finally get rid of shaded httpClient and wagon-http-shaded as well.
To switch transport use -Dmaven.resolver.transport with following values:
wagon - to use wagon (is default as well)native - to use resolver own highly optimized HTTP and FILE transport (supports "smart checksums")auto - to rely on resolver own discovery, or if another transport extension used
The selected transport can be seen in debug (-X) output on line [DEBUG] Using transporter XXX...
Issue Links:
- MNG-7614 Maven should translate transport configuration fully to resolver transports.
("incorporates")
Remote Links:
Backported to: 4.0.0-alpha-2, 3.9.0
Tamas Cservenak opened MNG-7454 and commented
We should include maven-resolver-transport-http (along with existing maven-resolver-transport-wagon) but retain Wagon as default transport, while offer ability for users to use http transport to utilize new resolver features like "smart checksums".
On positive side, this will finally get rid of shaded httpClient and wagon-http-shaded as well.
To switch transport use
-Dmaven.resolver.transportwith following values:wagon- to use wagon (is default as well)native- to use resolver own highly optimized HTTP and FILE transport (supports "smart checksums")auto- to rely on resolver own discovery, or if another transport extension usedThe selected transport can be seen in debug (-X) output on line
[DEBUG] Using transporter XXX...Issue Links:
("incorporates")
Remote Links:
Backported to: 4.0.0-alpha-2, 3.9.0