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/12/02 12:21:55 UTC

[jira] Commented: (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:comment-tabpanel&focusedCommentId=200254#action_200254 ] 

Brett Porter commented on MRM-1025:
-----------------------------------

the above has now been done. Along the way, several bugs have been fixed (usedBy and dependency tree now work more reliably and quickly) and some tests added.

While it works, the code is not production ready - it litters the home directory with property files and needs to be centralised. There is more testing to be added and there are probably some edge cases that remain problematic. In particular, Maven-1 formatted storage repositories is likely to not work.

Before moving to polishing, I'll continue proving the API by moving other archiva-database uses over to it, such as RSS, reporting, and any remaining bits of the webapp and XMLRPC.





> 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