[
https://issues.apache.org/jira/browse/MNG-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215873#comment-17215873
]
Michael Osipov commented on MNG-6581:
-------------------------------------
The entire magic happens in
{{org.eclipse.aether.internal.impl.DefaultDeployer.deploy(SyncContext,
RepositorySystemSession, DeployRequest)}}. It downloads metadata for all
artifacts, merges them, uploads all artifacts, then uploads all metadata.
> Maven deploys version metadata multiple times
> ---------------------------------------------
>
> Key: MNG-6581
> URL: https://issues.apache.org/jira/browse/MNG-6581
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.3.9, 3.5.0, 3.5.2, 3.5.3, 3.5.4, 3.6.0
> Reporter: Tamás Cservenák
> Priority: Blocker
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This causes problems like MDEPLOY-221 is.
> Problem:
> Maven deploys version metadata multiple times. Seems it is triggered by any
> plugin that attaches artifact to MavenProject?
> This happens with all 2.x m-deploy-p. 3.0.0-M1 fails.
> Expected:
> Maven deploy version (and any other) metadata only once with proper
> timestmaps (those that have the deployed artifacts) whatever count of
> attached artifacts are there.
> Reproducer:
> [https://github.com/cstamas/mvn-md-bug]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)