[
http://jira.codehaus.org/browse/MRM-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209018#action_209018
]
Maria Odea Ching commented on MRM-1321:
---------------------------------------
It's possible, there were a number of changes/fixes from 1.2.2 to 1.3. Would
you like to provide a test case and/or a fix for this?
> Snapshot is linking to oldest version in Archiva GUI
> ----------------------------------------------------
>
> Key: MRM-1321
> URL: http://jira.codehaus.org/browse/MRM-1321
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.3
> Environment: all
> Reporter: dtriphaus
>
> If i upload a Snapshot to archiva it shows up as Version
> 0.0.1-20100127.073805-1 and the Version of the 0.0.1-SNAPSHOT Artifact is
> also 0.0.1-20100127.073805-1. So if i download the jar from the orange box, i
> get the version 0.0.1-20100127.073805-1. Now i upload a later snapshot
> version to archiva: 0.0.1-20100127.074443-3. The Version shows up in the list
> of snapshots in archiva (other versions), but the Version is still set to
> 0.0.1-20100127.073805-1. So if i download the jar from the orange box it is
> still version 0.0.1-20100127.073805-1 and not the latest version.
> maven-metadata.xml is correct and builds get the latest version, but
> archiva-gui shows up the first uploaded snapshot. In Archiva 1.2.2 this was
> working correct. If the oldest snapshot gets purged, archiva uses the oldest
> still available version to show up as xxx-SNAPSHOT. Maybe some kind of
> sorting was changed?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
