[
https://issues.apache.org/jira/browse/MNG-7608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642808#comment-17642808
]
ASF GitHub Bot commented on MNG-7608:
-------------------------------------
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...
> Make Resolver native transport the default in Maven4
> ----------------------------------------------------
>
> Key: MNG-7608
> URL: https://issues.apache.org/jira/browse/MNG-7608
> Project: Maven
> Issue Type: Improvement
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.x-candidate, 4.0.0
>
>
> The ancient Wagon should be phased out, and "native" resolver transport
> should be the default in Maven4. This in start halves the HTTP request count
> toward Maven Central and any major MRM.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
