You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2020/10/25 08:50:00 UTC
[jira] [Comment Edited] (MRESOLVER-144) Maven Resolver deploys
version metadata multiple times
[ https://issues.apache.org/jira/browse/MRESOLVER-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220261#comment-17220261 ]
Michael Osipov edited comment on MRESOLVER-144 at 10/25/20, 8:49 AM:
---------------------------------------------------------------------
Wait a minute, it does *not* deploy the same JAR multiple times. All it does is to deploy the same GA metadata several times. You have correct metadata in any case. Inefficiency is a non-functional issue, but a bug. The actual outcome produces correct metadata.
The main problem is that Resolver would need to memorize the same of the current upload session and would require an explicit command to finalize it with the GA metadata upload. As of now, I don't see a way w/o modifying Resolver and its downstream consumers.
Please let me know how the partial fix makes better for your.
was (Author: michael-o):
Wait a minute, it does *not* deploy the same JAR multiple times. All it does is to deploy the same GA metadata several times. You have correct metadata in any case. Inefficiency is a non-functional issue, but a bug. The actual outcome produces correct metadata.
The main problem is that Resolver would need to memorize the same of the current upload session and would require an explicit command to finalize it with the GA metadata upload. As of now, I don't see a way w/o modifying Resolver and its downstream consumers.
> 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)