[
https://issues.apache.org/jira/browse/MRESOLVER-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov moved MNG-6581 to MRESOLVER-144:
-----------------------------------------------
Component/s: (was: Artifacts and Repositories)
resolver
Key: MRESOLVER-144 (was: MNG-6581)
Affects Version/s: (was: 3.5.4)
(was: 3.5.3)
(was: 3.6.0)
(was: 3.5.2)
(was: 3.5.0)
(was: 3.3.9)
1.6.1
Project: Maven Resolver (was: Maven)
> 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)