[jira] [Commented] (MNG-6581) Maven deploys version metadata multiple times
[
https://issues.apache.org/jira/browse/MNG-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215873#comment-17215873
]
Michael Osipov commented on MNG-6581:
-
The entire magic happens in
{{org.eclipse.aether.internal.impl.DefaultDeployer.deploy(SyncContext,
RepositorySystemSession, DeployRequest)}}. It downloads metadata for all
artifacts, merges them, uploads all artifacts, then uploads all metadata.
> Maven deploys version metadata multiple times
> -
>
> Key: MNG-6581
> URL: https://issues.apache.org/jira/browse/MNG-6581
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.3.9, 3.5.0, 3.5.2, 3.5.3, 3.5.4, 3.6.0
>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)
[jira] [Commented] (MNG-6581) Maven deploys version metadata multiple times
[ https://issues.apache.org/jira/browse/MNG-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215864#comment-17215864 ] Michael Osipov commented on MNG-6581: - I cannot really consider that this is a bug. For every artifact Maven Resolver (not Maven) has to retrieve the metadata from the repo. One could argue Resolver could cache the information, but what would be the implications? The question is: Is the multiple upload your problem or inconsistent timestamps in the metadata files in one reactor? > Maven deploys version metadata multiple times > - > > Key: MNG-6581 > URL: https://issues.apache.org/jira/browse/MNG-6581 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.3.9, 3.5.0, 3.5.2, 3.5.3, 3.5.4, 3.6.0 >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)
[jira] [Commented] (MNG-6581) Maven deploys version metadata multiple times
[ https://issues.apache.org/jira/browse/MNG-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17070068#comment-17070068 ] Hudson commented on MNG-6581: - Build succeeded in Jenkins: Maven TLP » maven » MNG-5868 #51 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5868/51/ > Maven deploys version metadata multiple times > - > > Key: MNG-6581 > URL: https://issues.apache.org/jira/browse/MNG-6581 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.3.9, 3.5.0, 3.5.2, 3.5.3, 3.5.4, 3.6.0 >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)
[jira] [Commented] (MNG-6581) Maven deploys version metadata multiple times
[ https://issues.apache.org/jira/browse/MNG-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069845#comment-17069845 ] Hudson commented on MNG-6581: - Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4 See https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/ > Maven deploys version metadata multiple times > - > > Key: MNG-6581 > URL: https://issues.apache.org/jira/browse/MNG-6581 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.3.9, 3.5.0, 3.5.2, 3.5.3, 3.5.4, 3.6.0 >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)
[jira] [Commented] (MNG-6581) Maven deploys version metadata multiple times
[ https://issues.apache.org/jira/browse/MNG-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023965#comment-17023965 ] Hudson commented on MNG-6581: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6071 #33 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6071/33/ > Maven deploys version metadata multiple times > - > > Key: MNG-6581 > URL: https://issues.apache.org/jira/browse/MNG-6581 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.3.9, 3.5.0, 3.5.2, 3.5.3, 3.5.4, 3.6.0 >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)
[jira] [Commented] (MNG-6581) Maven deploys version metadata multiple times
[ https://issues.apache.org/jira/browse/MNG-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916992#comment-16916992 ] Michael Osipov commented on MNG-6581: - [~eolivelli], no I have merged it as https://github.com/apache/maven/commit/8f1cac0b1c58c5b1ad26d38cbfd963d10f66d92a with a separate issue. I haven't even investigated this one. > Maven deploys version metadata multiple times > - > > Key: MNG-6581 > URL: https://issues.apache.org/jira/browse/MNG-6581 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.3.9, 3.5.0, 3.5.2, 3.5.3, 3.5.4, 3.6.0 >Reporter: Cservenak, Tamas >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.2#803003)
[jira] [Commented] (MNG-6581) Maven deploys version metadata multiple times
[
https://issues.apache.org/jira/browse/MNG-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916771#comment-16916771
]
Enrico Olivelli commented on MNG-6581:
--
[~michael-o] has this issue been fixed by
https://github.com/apache/maven/pull/252 ("upgrade modello") ?
I can't find a direct relation but JIRA links this issue to that PR and that PR
has been committed by you.
> Maven deploys version metadata multiple times
> -
>
> Key: MNG-6581
> URL: https://issues.apache.org/jira/browse/MNG-6581
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.3.9, 3.5.0, 3.5.2, 3.5.3, 3.5.4, 3.6.0
>Reporter: Cservenak, Tamas
>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.2#803003)
[jira] [Commented] (MNG-6581) Maven deploys version metadata multiple times
[ https://issues.apache.org/jira/browse/MNG-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915007#comment-16915007 ] Hudson commented on MNG-6581: - Build failed in Jenkins: Maven TLP » maven » MNG-6656 #7 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6656/7/ > Maven deploys version metadata multiple times > - > > Key: MNG-6581 > URL: https://issues.apache.org/jira/browse/MNG-6581 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.3.9, 3.5.0, 3.5.2, 3.5.3, 3.5.4, 3.6.0 >Reporter: Cservenak, Tamas >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.2#803003)
[jira] [Commented] (MNG-6581) Maven deploys version metadata multiple times
[ https://issues.apache.org/jira/browse/MNG-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16860265#comment-16860265 ] Hudson commented on MNG-6581: - Build succeeded in Jenkins: Maven TLP » maven » master #220 See https://builds.apache.org/job/maven-box/job/maven/job/master/220/ > Maven deploys version metadata multiple times > - > > Key: MNG-6581 > URL: https://issues.apache.org/jira/browse/MNG-6581 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.3.9, 3.5.0, 3.5.2, 3.5.3, 3.5.4, 3.6.0 >Reporter: Cservenak, Tamas >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 (v7.6.3#76005)
