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

Tamas Cservenak closed MNG-7845.
--------------------------------
    Resolution: Cannot Reproduce

Will reopen once we (if we) have response.

> Slow upload of artifacts to remote repository
> ---------------------------------------------
>
>                 Key: MNG-7845
>                 URL: https://issues.apache.org/jira/browse/MNG-7845
>             Project: Maven
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: 3.9.1
>            Reporter: Filip Pitak
>            Priority: Critical
>
> After an upgrade of maven from v3.3.9 to v3.9.1 the deployment of artifacts 
> to a remote repository via _*'mvn deploy'*_ has been substantially slowed 
> down. Disregarding the time for installing and other steps, the deployment of 
> artifacts went from +-40seconds to 6minutes. As our projects consists of 
> multiple modules, the total time of deployment jumped from 20minutes to 
> 1h20min. For our remote repository we are using Sonatype Nexus RepositoryOSS 
> 3.56.0-01.
> In the newer version maven has switched from Wagon to using "native HTTP", 
> which caused this issue.
> I've solved the problem by calling _*"mvn deploy  
> -Dmaven.resolver.transport=wagon"*_ and also downgrading the version of 
> Wagon. Various versions of Wagon had a different result in upload speeds:
>  
> ||Wagon version||Deploy speed||
> |2.7|25 sec.|
> |2.10|35 sec|
> |3.x.x|4 min.|
>  
> This solution is not viable in the long-run as it requires using an ancient 
> transport resolver and downgrading the version, which is not future-proof. A 
> similar solution of speeding up the deployment should be available when using 
> the default {*}{{maven-resolver-transport-http}} aka _native HTTP_ 
> transport{*}. Is there an existing implementation, which {*}{{*}}could be 
> used here?
>  



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

Reply via email to