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/05/04 07:22:12 UTC

[jira] Updated: (MRM-1384) move configuration into the content repository, persisted to the external configuration file

     [ http://jira.codehaus.org/browse/MRM-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRM-1384:
------------------------------

    Fix Version/s: Backlog

> move configuration into the content repository, persisted to the external configuration file
> --------------------------------------------------------------------------------------------
>
>                 Key: MRM-1384
>                 URL: http://jira.codehaus.org/browse/MRM-1384
>             Project: Archiva
>          Issue Type: Improvement
>    Affects Versions: 1.4
>            Reporter: Brett Porter
>             Fix For: Backlog
>
>
> several configuration options are repository specific, and it is likely plugins will need to contribute their own configuration options (Especially as some functionality, such as the proxy, is decoupled). It would be useful to be able to store this in the content repository and access it from the repository API. This would also give uniform access to the properties via any REST or XMLRPC APIs.
> The config should still be stored on disk in an editable format so that it can be easily maintained externally or pre-configured. This might mean that it needs to either use a separate part of the API to store it, or "mirror" the contents in some way.

-- 
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