[
https://issues.apache.org/jira/browse/COLLECTIONS-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010565#comment-15010565
]
Emmanuel Bourg commented on COLLECTIONS-582:
--------------------------------------------
Would it be possible to ask for a modification of the metadata file? The
versions deployed would remain, but maven-metadata.xml could at least point to
3.2.2 as the latest release. This happens automatically with every new release,
so it's legitimate to expect that for commons-collections 3.2.2.
> Maven repository metadata of Commons Collections in bad condition
> -----------------------------------------------------------------
>
> Key: COLLECTIONS-582
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-582
> Project: Commons Collections
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.2.2
> Reporter: Alexander Veit
>
> The metadata located at
> https://repo1.maven.org/maven2/commons-collections/commons-collections/maven-metadata.xml
> are in a bad condition.
> It states that latest version and release version is 20040616. Moreover, the
> list of versions does not reflect the actual release order.
> This makes it difficult to automatically check for new versions in our QA
> processes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
