On Fri, 13 Oct 2023 at 07:36, Tamás Cservenák wrote:
>
> Currently the names are like these:
> https://github.com/apache/maven/blob/maven-3.9.x/maven-core/src/main/java/org/apache/maven/internal/aether/DefaultRepositorySystemSessionFactory.java#L107-L109
>
> So "wagon", "native" (for
Currently the names are like these:
https://github.com/apache/maven/blob/maven-3.9.x/maven-core/src/main/java/org/apache/maven/internal/aether/DefaultRepositorySystemSessionFactory.java#L107-L109
So "wagon", "native" (for maven-resolver-transport-http), and "auto" (to
apply Resolver built-in auto
On Fri, 13 Oct 2023 at 05:52, Guillaume Nodet wrote:
>
> Le jeu. 12 oct. 2023 à 21:15, Tamás Cservenák a
> écrit :
>
> > 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
Le jeu. 12 oct. 2023 à 21:15, Tamás Cservenák a
écrit :
> 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):
> *
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)
*
