You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2022/12/02 07:24:12 UTC
[GitHub] [maven] cstamas opened a new pull request, #892: [MNG-7608] Make native transport the default
cstamas opened a new pull request, #892:
URL: https://github.com/apache/maven/pull/892
This immediately cuts in "half" the count of HTTP requests against Maven Central or any major MRM.
Altering the meaning of "default": is now same as "auto", but still leaving it in place for future, as "default" at some point may again become something different than "native".
---
https://issues.apache.org/jira/browse/MNG-7608
--
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: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven] olamy commented on pull request #892: [MNG-7608] Make native transport the default
Posted by GitBox <gi...@apache.org>.
olamy commented on PR #892:
URL: https://github.com/apache/maven/pull/892#issuecomment-1335937017
before this it was possible for users to use their own wagon impls.
How is it possible now?
--
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: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven] cstamas commented on pull request #892: [MNG-7608] Make native transport the default
Posted by GitBox <gi...@apache.org>.
cstamas commented on PR #892:
URL: https://github.com/apache/maven/pull/892#issuecomment-1336130709
Nothing of legacy is lost, resolver transport (since 3.0) was always like this:
```
maven +-> transport-wagon +-> wagon-http
| +-> wagon-foo
| +-> ...
+-> transport-http
+-> transport-jetty (or whatever)
```
All what happened here is the "transport-wagon" got it's original priority for resolver applied (is demoted). Hence, to use custom wagon, all you need is to set transport-wagon, and from there, everything is "as before". This change merely exposed (and reordered) the first level of "transort-*" nodes...
--
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: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven] cstamas commented on pull request #892: [MNG-7608] Make native transport the default
Posted by GitBox <gi...@apache.org>.
cstamas commented on PR #892:
URL: https://github.com/apache/maven/pull/892#issuecomment-1334944609
This PR needs more
--
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: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven] cstamas merged pull request #892: [MNG-7608] Make native transport the default
Posted by GitBox <gi...@apache.org>.
cstamas merged PR #892:
URL: https://github.com/apache/maven/pull/892
--
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: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org