[
https://issues.apache.org/jira/browse/MRESOLVER-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246734#comment-17246734
]
Tamás Cservenák commented on MRESOLVER-144:
-------------------------------------------
Looks very much same as MDEPLOY-274: m-d-p 2.8.2 works okay, 3.0.0-M1 gets 401.
{quote}Without looking into MDEPLOY, it could also be maven-artifact-transfer.
{quote}
It is clearly there: compare DeployMojo 2.8.2 and 3.0.0-M1 (or master) and is
clear: former invokes Deployer multiple times, latter just once. Or in other
words, {{RepositorySystem#deploy}} is called multiple times in first, and once
it second case.
> 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
> Assignee: Michael Osipov
> 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)
