You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2015/05/26 10:38:17 UTC
[jira] [Updated] (KARAF-545) Config file creation and update from
features descriptor
[ https://issues.apache.org/jira/browse/KARAF-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-545:
---------------------------------------
Fix Version/s: (was: 4.0.0.M3)
> Config file creation and update from features descriptor
> --------------------------------------------------------
>
> Key: KARAF-545
> URL: https://issues.apache.org/jira/browse/KARAF-545
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-feature
> Reporter: Jean-Baptiste Onofré
>
> I have a features descriptor containing:
> <features>
> <feature name="my" version="1.0">
> <config name="my.cfg">
> first.property=first.value
> second.property=second.value
> </config>
> <bundle .../>
> <bundle .../>
> </feature>
> </features>
> It could be helpful that the FeaturesDeployer create the etc/my.cfg file.
> Like this:
> - the configuration file is created and archived
> - the config:list command displays this configuration
> More over, when the etc/my.cfg file already exists and we try to update the feature, the FeaturesDeployer should add new properties in the config file (and let the existing ones).
> Finally, to be consisten, the maven features plugin should also create these config files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)