You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/02/23 09:23:06 UTC
[jira] Closed: (MRM-705) database scanning should be able to be run
after repository scanning
[ http://jira.codehaus.org/browse/MRM-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MRM-705.
----------------------------
Resolution: Won't Fix
Fix Version/s: (was: Backlog)
Assignee: Brett Porter
redundant
> database scanning should be able to be run after repository scanning
> --------------------------------------------------------------------
>
> Key: MRM-705
> URL: http://jira.codehaus.org/browse/MRM-705
> Project: Archiva
> Issue Type: Improvement
> Components: repository scanning
> Affects Versions: 1.0.1
> Reporter: Brett Porter
> Assignee: Brett Porter
>
> since after the initial processing both scans are quite fast, being able to put them together sequentially makes sense so that changes are reflected as quickly as possible
--
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