[
https://issues.apache.org/jira/browse/MRESOLVER-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-319:
--------------------------------------
Description:
Basic connector is able to perform parallel fetches. In same way, connector
should be improved to perform parallel uploads.
The new feature should be "dormant" by default (as every new feature), but user
should be able to enable it via configuration.
Two important implementation details:
* we need ONE transport to go from beginning to end thru the pipe (to init
transporter fully)
* metadata needs to be ordered V->A->G->ROOT as clients go opposite order (to
not let any window of opportunity of failed build)
was:
Basic connector is able to perform parallel fetches. In same way, connector
should be improved to perform parallel uploads.
The new feature should be "dormant" by default (as every new feature), but user
should be able to enable it via configuration.
Two important implementation details
> Support parallel deploy
> -----------------------
>
> Key: MRESOLVER-319
> URL: https://issues.apache.org/jira/browse/MRESOLVER-319
> Project: Maven Resolver
> Issue Type: New Feature
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 1.9.5
>
>
> Basic connector is able to perform parallel fetches. In same way, connector
> should be improved to perform parallel uploads.
> The new feature should be "dormant" by default (as every new feature), but
> user should be able to enable it via configuration.
> Two important implementation details:
> * we need ONE transport to go from beginning to end thru the pipe (to init
> transporter fully)
> * metadata needs to be ordered V->A->G->ROOT as clients go opposite order (to
> not let any window of opportunity of failed build)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
