cstamas commented on PR #231: URL: https://github.com/apache/maven-resolver/pull/231#issuecomment-1366133370
Just to clear up: the fact we have here 5 (7 to be exact) transports, that does not mean we need to deliver all these with Maven. Or in other words, transport-http, transport-file and transport-classpath was present since day 0 (of resolver existence), but _no Maven included it so far_. Maven 3.9/4.0 will be the first that will include transport-http. There are 4 transports already (file, http, wagon, classpath), and this PR adds 3 new modules. But, the thing is, these are all for HTTP protocol (when protocol of remote repository is HTTP/HTTPS). These are the "old" ones: * wagon * http (aka "native") While these are new: * java11 * jetty * okhttp New ones are all HTTP/2 capable. Personally, from new ones, I'd remove okhttp (cons: pulls in kotlin runtime and is slowest H2 client). Java11 and Jetty were really close to each other. In short: the fact a transport is present here, does not mean _we must ship it_, as the case of transport-classpath and transport-http shows (they were present since day 0 of resolver, but never shipped). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
