[
http://jira.codehaus.org/browse/MRM-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100328
]
Maria Odea Ching edited comment on MRM-416 at 6/22/07 7:12 AM:
---------------------------------------------------------------
Fixed in -r549792
Fix was:
- Added DatabaseSearch class for querying from the database (This could be used
for future database queries so there is only one entry point for all
db queries)
- Added ArtifactsByChecksumConstraint to be used for querying artifacts by
checksum (either sha1, md5 or both)
- Updated "artifact" result of findArtifact action in xwork.xml
- Updated SearchAction to find an artifact (using checksums) in the database
instead of in the indices
- Updated results.jsp to accomodate when the results came from the database
instead of the SearchResults that is for index searching
- Deleted ArtifactsBySha1Constraint and its test, replaced by
ArtifactsByChecksumConstraint
- Created tests for the new classes added
Please verify.. thanks :)
was:
Fixed in -r549792
Fix was:
- Added DatabaseSearch class for querying from the database (This could be used
for future database queries so there is only one entry point for all
db queries)
- Added ArtifactsByChecksumConstraint to be used for querying artifacts by
checksum (either sha1, md5 or both)
- Updated "artifact" result of findArtifact action in xwork.xml
- Updated SearchAction to find an artifact (using checksums) in the database
instead of in the indices
- Updated results.jsp to accomodate when the results came from the database
instead of the SearchResults that is for index searching
- Deleted ArtifactsBySha1Constraint and its test, replaced by
ArtifactsByChecksumConstraint
- Created tests for the new classes added
> Find artifact does not work.
> ----------------------------
>
> Key: MRM-416
> URL: http://jira.codehaus.org/browse/MRM-416
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0-alpha-2
> Reporter: Henry S. Isidro
> Assignee: Maria Odea Ching
> Fix For: 1.0-alpha-2
>
>
> Finding an artifact always shows the 'No results found' message even though
> the artifact that is being looked for is in the repository.
--
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
