Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Mon, 6 Feb 2017 15:09:41 +0000 (UTC)
From: "Christian Schneider (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12502970.1301539629000.6270.1486393781729@Atlassian.JIRA>
In-Reply-To: <JIRA.12502970.1301539629000@Atlassian.JIRA>
References: <JIRA.12502970.1301539629000@Atlassian.JIRA> <JIRA.12502970.1301539629368@jira-lw-us.apache.org>
Subject: [jira] [Work stopped] (KARAF-550) Make it easier to add additional
 custom property files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 06 Feb 2017 15:09:46 -0000


     [ https://issues.apache.org/jira/browse/KARAF-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on KARAF-550 stopped by Christian Schneider.
-------------------------------------------------
> Make it easier to add additional custom property files
> ------------------------------------------------------
>
>                 Key: KARAF-550
>                 URL: https://issues.apache.org/jira/browse/KARAF-550
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-core
>            Reporter: Andreas Pieber
>            Assignee: Andreas Pieber
>
> The current custom.properties approach has some drawbacks in case you have a structure like karaf <- other framework project like smx <- client project. In this case you may like to add some custom.properties which should not be as easy to overwrite by the client. For example you want to provide a default configuration for activemq webconsole, or some other properties. As the framework you can overwrite the config.properties file now and include additional property files used this way but this has the drawback that you, as framework developer, have to upgrade the config.properties with each karaf upgrade. I've two options in minds:
> <<edit>>
> After some lengthy discussion with Guillaume and JB we come to the following conclusion for this issue:
> In addition to providing directly the files which should be used in config.properties in system.properties and config.properties a pattern could be defined in config.properties and system.properties (besides the "regular" includes) to allow that client projects/frameworks could easily add additional config files which are included without any additional work


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)