[
http://jira.codehaus.org/browse/MRM-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191283#action_191283 ]
Maria Odea Ching commented on MRM-1056:
---------------------------------------
Docs updated to reflect these changes in trunk -r816092.
> Option to force scanning of an artifact/repository regardless of file dates
> ---------------------------------------------------------------------------
>
> Key: MRM-1056
> URL:
http://jira.codehaus.org/browse/MRM-1056> Project: Archiva
> Issue Type: Improvement
> Affects Versions: 1.1.2
> Reporter: Wendy Smoak
> Assignee: Maria Odea Ching
> Fix For: 1.2.3
>
>
> Often I try to browse an artifact and see "Unable to find project model" even though I know the artifact is in the repository.
> By default when Archiva scans a repo, it only "sees" files added since the last time the scan was run.
> Currently the only way I know to re-set it is to touch the files on disk so they appear newer, or delete the database so that Archiva will start over with scanning, neither of which is ideal.
> I need a way to force scanning of artifact(s) or an entire repository, regardless of the file dates.
> If the 'Last Scanned' date on the Repositories page were configurable, that would allow me to set the date far back in time so that all files would appear to be "new" and it would scan everything again.
> Or, some way to give it a groupId or groupId+artifactId and have it go fix its database for that subset of the repo contents.
--
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
