Howdy,

As part of the new Resolver major version, one of the goals is to introduce
HTTP/2 capable transports. And as always, naming...

Current transport module names (==artifactId) are (already quite long for
my taste):
* maven-resolver-transport-classpath (CP transport, is not HTTP, just FTR)
* maven-resolver-transport-file (file transport, is not HTTP, just FTR)
* maven-resolver-transport-http (uses Apache HttpClient 4.x, HTTP/1.1
capable)
* maven-resolver-transport-wagon (uses Wagon, so is not only HTTP, HTTP/1.1
capable)

And now the two new contenders:
* Java11+ java.net.http.HttpClient based (HTTP/2 capable)
* Java11+ Jetty12 based (HTTP/2 capable)

So, the major question is how to name these modules (== artifactId)?

* maven-resolver-transport-java11?
* maven-resolver-transport-jetty12?

Maybe some form of proto+imple?

* maven-resolver-transport-http2-java11 (or shorter
maven-resolver-transport-h2-java11)
* maven-resolver-transport-http2-jetty (or shorter
maven-resolver-transport-h2-jetty)

But there are not ONLY HTTP/2 (they are also HTTP/1.1 capable as well).
Also, the Jetty version matters, so once in future there will be Jetty13
etc...

Ideas welcome.

Thanks
T

PS: Given java.net.http.HttpClient based transport will be dependency-less,
it reminds me of good old wagon-http-lightweight, but unlike wagon one
(that was quite limited), this will be fully capable transport.

Reply via email to