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

Tamas Cservenak commented on MRESOLVER-32:
------------------------------------------

This assessment above of mine is completely wrong... This actually seems 
trivial to implement, in case we have one incoming deploy request that contains 
all deploy-able stuff (artifacts), and resolver sorts everything else out, just 
like it happens when resolving artifacts (similarly, uses thread pool of 5 
threads by default).

> Support parallel artifact/metadata uploads
> ------------------------------------------
>
>                 Key: MRESOLVER-32
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-32
>             Project: Maven Resolver
>          Issue Type: Improvement
>          Components: Resolver
>            Reporter: Matt Nelson
>            Priority: Major
>
> When using the {{maven-deploy-plugin}} with the {{deployAtEnd}} property on a 
> large reactor the deployment process can take a considerable amount of time. 
> I have a large reactor(50+ modules) where the upload takes 50% of the build 
> time, 10 out of 20 minutes solely on the upload.



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

Reply via email to