Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Tue, 12 Jul 2011 22:32:59 +0000 (UTC)
From: "Andreas Pieber (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: 
 <515900708.8005.1310509979907.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <28406462.203081295996743728.JavaMail.jira@thor>
Subject: [jira] [Commented] (KARAF-418) Allow configurations (from ./etc) to
 be placed in a database.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/KARAF-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064206#comment-13064206 ] 

Andreas Pieber commented on KARAF-418:
--------------------------------------

Just to attach Achims question from IRC here:

(12:23:23 AM) anierbeck: pieber: btw. do we still need this one? https://issues.apache.org/jira/browse/KARAF-418

Good question. I would rather say no. Cellar should does most of the requirements defined here. @Mike: what do you think?

> Allow configurations (from ./etc) to be placed in a database.
> -------------------------------------------------------------
>
>                 Key: KARAF-418
>                 URL: https://issues.apache.org/jira/browse/KARAF-418
>             Project: Karaf
>          Issue Type: Brainstorming
>          Components: karaf-config
>            Reporter: Michael Van Geertruy
>             Fix For: 3.1.0
>
>
> There's been an ongoing dialogue on the dev's mailing list to discuss whether or not to allow configurations to be placed in a database instead of in the ./etc directory.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira