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é (Created JIRA)" <ji...@apache.org> on 2011/10/28 11:46:32 UTC
[jira] [Created] (KARAF-970) feature tag doesn't create
the cfg file
feature <config/> tag doesn't create the cfg file
-------------------------------------------------
Key: KARAF-970
URL: https://issues.apache.org/jira/browse/KARAF-970
Project: Karaf
Issue Type: Bug
Components: karaf-config, karaf-features
Affects Versions: 2.2.4
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Fix For: 2.2.5, 3.0.0
In a features XML descriptor, if we use:
<config id="my.pid">
key = value
</config>
we don't have a etc/my.pid.cfg file. I make sense to create the corresponding config file (and add a property in org.apache.karaf.features.cfg to define the default behavior).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (KARAF-970) feature tag doesn't create
the cfg file
Posted by "Jean-Baptiste Onofré (Resolved JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved KARAF-970.
----------------------------------------
Resolution: Won't Fix
<configfile/> has to be used instead.
> feature <config/> tag doesn't create the cfg file
> -------------------------------------------------
>
> Key: KARAF-970
> URL: https://issues.apache.org/jira/browse/KARAF-970
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-config, karaf-feature
> Affects Versions: 2.2.4
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.2.6, 3.0.0
>
>
> In a features XML descriptor, if we use:
> <config id="my.pid">
> key = value
> </config>
> we don't have a etc/my.pid.cfg file. I make sense to create the corresponding config file (and add a property in org.apache.karaf.features.cfg to define the default behavior).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-970) feature tag doesn't create
the cfg file
Posted by "Jean-Baptiste Onofré (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-970:
---------------------------------------
Issue Type: Improvement (was: Bug)
> feature <config/> tag doesn't create the cfg file
> -------------------------------------------------
>
> Key: KARAF-970
> URL: https://issues.apache.org/jira/browse/KARAF-970
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-config, karaf-features
> Affects Versions: 2.2.4
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.2.5, 3.0.0
>
>
> In a features XML descriptor, if we use:
> <config id="my.pid">
> key = value
> </config>
> we don't have a etc/my.pid.cfg file. I make sense to create the corresponding config file (and add a property in org.apache.karaf.features.cfg to define the default behavior).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-970) feature tag doesn't create
the cfg file
Posted by "Jean-Baptiste Onofré (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-970:
---------------------------------------
Fix Version/s: (was: 2.2.5)
2.2.6
> feature <config/> tag doesn't create the cfg file
> -------------------------------------------------
>
> Key: KARAF-970
> URL: https://issues.apache.org/jira/browse/KARAF-970
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-config, karaf-features
> Affects Versions: 2.2.4
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.2.6, 3.0.0
>
>
> In a features XML descriptor, if we use:
> <config id="my.pid">
> key = value
> </config>
> we don't have a etc/my.pid.cfg file. I make sense to create the corresponding config file (and add a property in org.apache.karaf.features.cfg to define the default behavior).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (KARAF-970) feature tag doesn't create
the cfg file
Posted by "Jamie goodyear (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear closed KARAF-970.
--------------------------------
> feature <config/> tag doesn't create the cfg file
> -------------------------------------------------
>
> Key: KARAF-970
> URL: https://issues.apache.org/jira/browse/KARAF-970
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-config, karaf-feature
> Affects Versions: 2.2.4
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.2.6, 3.0.0
>
>
> In a features XML descriptor, if we use:
> <config id="my.pid">
> key = value
> </config>
> we don't have a etc/my.pid.cfg file. I make sense to create the corresponding config file (and add a property in org.apache.karaf.features.cfg to define the default behavior).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira