[ 
https://issues.apache.org/jira/browse/MNG-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MNG-6254:
--------------------------------
    Summary: Clarification on <versions> sorting in Repository Metadata  (was: 
Clarificatin on <versions> sorting in Repository Metadata)

> Clarification on <versions> sorting in Repository Metadata
> ----------------------------------------------------------
>
>                 Key: MNG-6254
>                 URL: https://issues.apache.org/jira/browse/MNG-6254
>             Project: Maven
>          Issue Type: Improvement
>          Components: Artifacts and Repositories
>    Affects Versions: 3.5.0
>            Reporter: Markus Karg
>            Priority: Major
>
> The document 
> http://maven.apache.org/ref/3.3.9/maven-repository-metadata/repository-metadata.html
>  explains that <versions> does contain a _List_<Version>, hence is _sorted_.
> When pulling _real _metadata from Maven Central, e. g. 
> http://repo.maven.apache.org/maven2/javax/ws/rs/jsr311-api/maven-metadata.xml,
>  it is apparent that the content of <version> is _not_ sorted (in this 
> example, 1.1-ea is listed _after_ 1.1, which is a violation of the sorting, 
> because -ea must be listed _before_ 1.1). So effectively Maven Central 
> devliers _unsorted_ versions.
> Also, the effectively listed XSD 
> http://maven.apache.org/xsd/metadata-1.1.0.xsd is nonexistent, so cannot be 
> looked but whether Maven Central is wrong, or whether actually the 
> specification should say it must be Set<Version> instead of List<Version>.
> To sum up, there should be a clarification whether <version> must be sorted 
> according to the Maven Version Numbering Schema, whether it must be Set vs 
> List, and whether the missing XSD should be uploaded.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to