You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamás Cservenák (Jira)" <ji...@apache.org> on 2020/10/17 16:42:00 UTC

[jira] [Commented] (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=17215939#comment-17215939 ] 

Tamás Cservenák commented on MRESOLVER-144:
-------------------------------------------

{quote} The question is: Is the multiple upload your problem or inconsistent timestamps in the metadata files in one reactor? {quote}

Both

> 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)