karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Commented] (KARAF-545) Config file creation and update from features descriptor
Date Sat, 02 Apr 2011 09:02:05 GMT

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

Jean-Baptiste Onofré commented on KARAF-545:

I was thinking it was the case also but some users reported that the configuration file are
not created from the features descriptor. I made a quick test and it's the case.
It's maybe a bug.

I'm gonna take a look.

> 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
>            Reporter: Jean-Baptiste Onofré
>             Fix For: 3.0.0
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message