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 2008/07/02 03:30:26 UTC
[jira] Updated: (MRM-848) Pre-configured repositories initially
appear to be empty
[ http://jira.codehaus.org/browse/MRM-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-848:
-----------------------------
Priority: Minor (was: Major)
Assignee: (was: Brett Porter)
Fix Version/s: (was: 1.1)
1.2
I'm concerned about throwing in a scan-on-startup due to the cost, and it's not trivial to detect whether a repository has already been scanned at that point of initialisation. Will take a closer look in a future version but I think this is minor.
> Pre-configured repositories initially appear to be empty
> --------------------------------------------------------
>
> Key: MRM-848
> URL: http://jira.codehaus.org/browse/MRM-848
> Project: Archiva
> Issue Type: Improvement
> Components: repository scanning
> Affects Versions: 1.0.2
> Reporter: Wendy Smoak
> Priority: Minor
> Fix For: 1.2
>
>
> If you pre-configure a populated repository, Archiva does not display the content immediately when you start the application.
> I think it should scan and index the repositories on startup, or possibly on the 'first' startup (when the database and index are empty.)
--
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