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-3100) Add Option To Create Config Files For Feature Configs Instead Of Importing Directly Into Config Admin
Date Wed, 06 Jan 2016 10:17:40 GMT

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

Jean-Baptiste Onofré commented on KARAF-3100:
---------------------------------------------

Actually, instead of adding a new property, I'm just leverage the same logic as config:* commands:
I use a updateStorage() method. So the <config/> element will automatically result to
a cfg file in the etc folder.

> Add Option To Create Config Files For Feature Configs Instead Of Importing Directly Into
Config Admin
> -----------------------------------------------------------------------------------------------------
>
>                 Key: KARAF-3100
>                 URL: https://issues.apache.org/jira/browse/KARAF-3100
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-feature
>    Affects Versions: 3.0.1
>            Reporter: Gareth Collins
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 3.0.6, 4.0.4
>
>
> I have created a pull request for this here:
> https://github.com/apache/karaf/pull/43
> As the title says, this allows karaf to be configured to output feature configurations
to config file...which I believe are easier to manage. Let me know what you think. If it looks
OK, would it be possible to merge soon (e.g. karaf 3.0.2 :))? The changes are very localized.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message