[
http://jira.codehaus.org/browse/MRM-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194652#action_194652
]
Brett Porter commented on MRM-1033:
-----------------------------------
that should be fine given that we have the "force scan" mode for other cases
now.
> Changing the location of a scanned repository results to the contents of the
> new location not getting indexed
> -------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1033
> URL: http://jira.codehaus.org/browse/MRM-1033
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning
> Affects Versions: 1.0, 1.1, 1.2-M1
> Reporter: Maria Odea Ching
> Fix For: 1.2.3
>
> Attachments: MRM-1033-new.patch, MRM-1033.patch
>
>
> For example, you have a repository 'test' which already has contents and is
> located at '../test/'. The repository has already been scanned and indexed.
> Now, you would like to point repository 'test' to a different repository. So
> you change it's location to '../another.repository/'. You wouldn't be able to
> index the artifacts in ../another.repository since the 'test' repository is
> already considered 'scanned' and the time stamp of the artifacts are older
> than the last scanning.
--
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
