[
https://issues.apache.org/jira/browse/MRESOLVER-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246536#comment-17246536
]
Tamás Cservenák commented on MRESOLVER-144:
-------------------------------------------
But, regarding this issue, did a bit of digging. Problem is following:
maven-deploy-plugin 2.x (2.8.2 latest in this moment) basically does "two phase
deploy" if am not mistaken: deploys project artifact and then deploys attached
artifact(s). Resolver hence "rinse and repeats" (with a diff, that
maven-metadata.xml is "fresh" on 2nd time). Hence, it performs two merges and
two uploads.
As I see, the upcoming maven-deploy-plugin 3.x (3.0.0-M1 in this moment)
*should solve* double metadata deploy as well, but it currently fails w/ test
project (seems does not pick up credentials for deploy).
> Maven Resolver deploys version metadata multiple times
> ------------------------------------------------------
>
> Key: MRESOLVER-144
> URL: https://issues.apache.org/jira/browse/MRESOLVER-144
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
> Affects Versions: 1.6.1
> 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)
