[jira] [Commented] (MNG-7454) Include resolver-transport-http in Maven

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

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

Hudson commented on MNG-7454:
-----------------------------

Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7448 #2

See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7448/2/

> Include resolver-transport-http in Maven
> ----------------------------------------
>
>                 Key: MNG-7454
>                 URL: https://issues.apache.org/jira/browse/MNG-7454
>             Project: Maven
>          Issue Type: New Feature
>          Components: Dependencies
>            Reporter: Tamás Cservenák
>            Assignee: Tamás Cservenák
>            Priority: Major
>             Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> We should include maven-resolver-transport-http (along with existing maven-resolver-transport-wagon) but retain Wagon as default transport, while offer ability for users to use http transport to utilize new resolver features like "smart checksums".
> On positive side, this will finally get rid of shaded httpClient and wagon-http-shaded as well.
> To switch transport use {{-Dmaven.resolver.transport}} with following values:
>  * {{wagon}} - to use wagon (is default as well)
>  * {{native}} - to use resolver own highly optimized HTTP and FILE transport (supports "smart checksums")
>  * {{auto}} - to rely on resolver own discovery, or if another transport extension used
> The selected transport can be seen in debug (-X) output on line `[DEBUG] Using transporter XXX...`



--
This message was sent by Atlassian Jira
(v8.20.7#820007)