You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2022/02/22 07:24:00 UTC
[jira] [Commented] (MNG-5180) Versioning's snapshot version list is not included in metadata merge
[ https://issues.apache.org/jira/browse/MNG-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495909#comment-17495909 ]
Konrad Windszus commented on MNG-5180:
--------------------------------------
I think the logic for merging {{versioning->snapshotVersions}} should be as follows according to https://maven.apache.org/ref/3.8.3/maven-repository-metadata/repository-metadata.html:
# classifier, extension and value act as key in the list
# every item in the list must have a unique key
# if an item with the same key is already in the list, the merged {{updated}} value should be used in the resulting item
The {{versioning->snapshotVersion}} should always contain the most recent item, i.e. the one from the {{snapshotVersions}} list with the most recent updated timestamp.
[~michael-o] WDYT?
> Versioning's snapshot version list is not included in metadata merge
> ----------------------------------------------------------------------
>
> Key: MNG-5180
> URL: https://issues.apache.org/jira/browse/MNG-5180
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.0.3
> Reporter: Noam Y. Tenne
> Assignee: Michael Osipov
> Priority: Major
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.x-candidate
>
> Attachments: MavenMetadataSnapshotVersionsMergeTest.java
>
>
> Versioning#snapshotVersions is not being merged when using Metadata#merge.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)