karaf-issues mailing list archives

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

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

Ioannis Canellos commented on KARAF-545:
----------------------------------------

Doesn't it do that already?

If I am not mistaken even some of the core karaf features add/update configuration the way
you described.

For example here's our http feature:

<feature name="http" version="${project.version}" resolver="(obr)">
        <configfile finalname="/etc/jetty.xml">mvn:org.apache.karaf/apache-karaf/${project.version}/xml/jettyconfig</configfile>
                <config name="org.ops4j.pax.web">
                    org.osgi.service.http.port=8181
                    javax.servlet.context.tempdir=${karaf.data}/pax-web-jsp
                    org.ops4j.pax.web.config.file=${karaf.base}/etc/jetty.xml
                </config>


> 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

Mime
View raw message