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 2009/11/20 01:58:55 UTC
[jira] Updated: (MRM-1025) make the archiva database an optional
part of the installation
[ http://jira.codehaus.org/browse/MRM-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1025:
------------------------------
Fix Version/s: (was: Backlog)
1.3
the first steps of this have been done
- started a trivial metadata content repository implementation and consumer to generate metadata. This needs much more work to be useful, but gives the right API hooks (see r721955)
- split scanning from the repository layer (see r722004) - this means some code that needed scanning need not depend on the repository-layer (and therefore archiva-model)
- removed database cleanup consumers, relying on "events" from when Archiva notices a deletion (See note below)
- removed some unused database consumers (see MRM-1281)
- split the scheduler into modules to isolate database and indexer dependent code, so that the nexus index consumer need not have a dependency on the database (see r882207)
Note that currently:
- detecting deleted files on the filesystem and updating the index / database is non-functional (see r723334)
> make the archiva database an optional part of the installation
> --------------------------------------------------------------
>
> Key: MRM-1025
> URL: http://jira.codehaus.org/browse/MRM-1025
> Project: Archiva
> Issue Type: Task
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.3
>
>
--
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