[
https://issues.apache.org/jira/browse/MRESOLVER-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689331#comment-17689331
]
ASF GitHub Bot commented on MRESOLVER-319:
------------------------------------------
cstamas commented on PR #245:
URL: https://github.com/apache/maven-resolver/pull/245#issuecomment-1431993162
Yes, this is definitely some concurrency problem of transport-http, more
precisely, initial population of auth cache and shared state,
Unsure would Wagon be better, as I see it keeps AuthCache per transport
instance (per HttpWagon instance that is created per-lookup, not a singleton),
while transport-http during lifetime of a session... (so it does Auth dance
once per session, and caches auth, Wagon does auth dance per transport
instance,, ie. per module deploy in multi module project).
> 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)
