[
https://issues.apache.org/jira/browse/MRESOLVER-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246534#comment-17246534
]
Tamás Cservenák edited comment on MRESOLVER-144 at 12/9/20, 1:45 PM:
---------------------------------------------------------------------
Tested maven master 95ee8908370744153531aa2e80a9bce93dc5d9bc (it has your
commit 72688805c4f95f8ab4ca9ab2ac2cd114667790c9 as well). Tested it by building
and deploying maven itself (the same hash as 1st one) :D
W/ 3.6.3 as expected, each deployed (snapshot) module had different timestamp
on deploy
W/ master (4.0.0-alpha-1-SNAPSHOT) each deployed (snapshot) module had *same*
timestamp on deploy.
+1
was (Author: cstamas):
Tested maven master 95ee8908370744153531aa2e80a9bce93dc5d9bc (it has your
commit 72688805c4f95f8ab4ca9ab2ac2cd114667790c9 as well). Tested it by building
maven (same hash as 1st one) :D
W/ 3.6.3 as expected, each deployed (snapshot) module had different timestamp
on deploy
W/ master (4.0.0-alpha-1-SNAPSHOT) each deployed (snapshot) module had *same*
timestamp on deploy.
+1
> 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)
