[jira] [Commented] (MNG-7608) Make Resolver native transport the default in Maven4

["Tamas Cservenak (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-7608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17640192#comment-17640192 ] 

Tamas Cservenak commented on MNG-7608:
--------------------------------------

This requires IT changes:
 * MavenITmng3652UserAgentHeaderTest.testmng3652_AdditionnalHttpHeaderConfiguredInSettings
 * MavenITmng3652UserAgentHeaderTest.testmng3652_UserAgentConfiguredInSettings
 * MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings
 * MavenITmng7470ResolverTransportTest.testResolverTransportDefault (trivial, "default" is not anymore Wagon)

Out of others for sure some use archaic (Maven2) way of plexus configuration to set headers and/or timeout settings (instead of common resolver configuration as explained [https://maven.apache.org/resolver/configuration.html] )

> 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)