You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamás Cservenák (Jira)" <ji...@apache.org> on 2022/09/21 06:58:00 UTC

[jira] [Closed] (MRESOLVER-121) Deprecate HTTP transport in favor of Wagon

     [ https://issues.apache.org/jira/browse/MRESOLVER-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tamás Cservenák closed MRESOLVER-121.
-------------------------------------
    Resolution: Won't Fix

Wagon is Maven2 and has many shortcomings, moreover the "native" resolver HTTP had many upgrades and useful features Wagon will NEVER support, like inlined checksums. Moreover, due deeply layered nature of Wagon, native transport is snappier as well. Hence, IMO keeping both of them is good for now, Maven is already able to select between transports, and it is just benefiting users...

> Deprecate HTTP transport in favor of Wagon
> ------------------------------------------
>
>                 Key: MRESOLVER-121
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-121
>             Project: Maven Resolver
>          Issue Type: Dependency upgrade
>          Components: Resolver
>            Reporter: Elliotte Rusty Harold
>            Priority: Major
>
> This duplicates the functionality of the Wagon HTTP Provider, and isn't syncing up well with the latest Apache http transports. Specifically deprecate (and eventually remove) the maven-resolver-transport-http artifact in favor of the maven-resolver-transport-wagon artifact.
> See https://github.com/apache/maven-resolver/pull/48 for some more info.
> First we need to make sure one can use Resolver with Wagon and its providers outside of Maven space and especially with Resolver Ant Tasks.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)