[
https://issues.apache.org/jira/browse/MRESOLVER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17683846#comment-17683846
]
ASF GitHub Bot commented on MRESOLVER-32:
-----------------------------------------
michael-o commented on PR #237:
URL: https://github.com/apache/maven-resolver/pull/237#issuecomment-1415763278
> Ok, will do it, but sequentially, as I don't see how to create these 3 PRs
simultaneously without conflicts against each other, and I would not like to
spend time on fixing conflicts after each merge, just for "purity". So, please
then, be prepared for snappy reviews 😉
>
> In other words, having these 3 commits separate is okay, but will not
allow their initial purpose (for example to roll back one of them) as all 3 are
quite interleaving with each other.
Layered, sequentically, of course. Not in parallel.
> 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
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 1.9.5
>
>
> 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)
