[jira] Closed: (MRM-426) Search does not work for snapshots because of different version values in index and database when the snapshot version is unique

["Maria Odea Ching (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MRM-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching closed MRM-426.
--------------------------------

    Resolution: Fixed

Fixed in -r558795

Fix:
- Added and modified code for handling snapshots (if the versions of a specific artifact snapshot are only timestamped versions, add a 
generic snapshot which is pointing to the latest timestamp version) in DefaultRepositoryBrowsing and ProjectModelToDatabaseConsumer.
- Updated pom validations in ProjectModelToDatabaseConsumer - handling of timestamped versions were considered
- Added isUniqueSnapshot(..) and isGenericSnapshot(..) in VersionUtil
- Added new attribute 'modelVersion' in DependencyTreeTag to get the in-pom version. Did not use the version attribute so as to retain the 
actual version being browsed. Also updated DependencyTree
- Updated the ff. pages for the version to be displayed: artifactInfo.jspf, showArtifact.jsp, dependencyTree.jsp and artifactDecorator.jsp
- Updated the version in SearchResultHit


> Search does not work for snapshots because of different version values in index and database when the snapshot version is unique
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRM-426
>                 URL: http://jira.codehaus.org/browse/MRM-426
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0-alpha-2
>            Reporter: Maria Odea Ching
>            Assignee: Maria Odea Ching
>
> When an artifact with unique snapshots is searched from Archiva, the search result would contain different hits for that artifact which has the same version but when you click the version to browse the artifact.. an ObjectNotFound error is returned. Below is an example of this behavior.
> The artifact to be searched is castor-anttasks. Let's say it has 3 SNAPSHOT versions 1.1.2-20070427.065136-1, 1.1.2-20070506.163513-2 and 1.1.2-20070506.163513-3 in the repository, and the path to this artifact is [REPO]/org/codehaus/castor/castor-anttasks/1.1.2-SNAPSHOT.
> The search results would then look like this:
> Hits: 3 of 3
> castor-anttasks
> org / codehaus / castor / castor-anttasks | Version(s): 1.1.2-SNAPSHOT
> castor-anttasks
> org / codehaus / castor / castor-anttasks | Version(s): 1.1.2-SNAPSHOT
> castor-anttasks
> org / codehaus / castor / castor-anttasks | Version(s): 1.1.2-SNAPSHOT
> When you click either of the versions to browse the artifact, what you would get is this error:
> 'Unable to find project model for [org.codehaus.castor:castor-anttasks:1.1.2-SNAPSHOT]'

-- 
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