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 2011/03/30 12:26:05 UTC
[jira] [Created] (KARAF-545) Config file creation and update from
features descriptor
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
[jira] [Updated] (KARAF-545) Config file creation and update from
features descriptor
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ 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: 3.1.0
> 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, 3.1.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
[jira] [Updated] (KARAF-545) Config file creation and update from
features descriptor
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-545:
---------------------------------------
Component/s: karaf-features
Assignee: Jean-Baptiste Onofré
> 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-features
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.0, 3.1.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
[jira] [Assigned] (KARAF-545) Config file creation and update from
features descriptor
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-545:
------------------------------------------
Assignee: (was: Jean-Baptiste Onofré)
> 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é
> Fix For: 3.1.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.
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] [Commented] (KARAF-545) Config file creation and update from
features descriptor
Posted by "Ioannis Canellos (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (KARAF-545) Config file creation and update from
features descriptor
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063374#comment-13063374 ]
Jean-Baptiste Onofré commented on KARAF-545:
--------------------------------------------
This issue should be tested as it should work (at least, it seems to work on karaf-2.2.x).
> 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-features
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.0, 3.1.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
[jira] [Commented] (KARAF-545) Config file creation and update from
features descriptor
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (KARAF-545) Config file creation and update from
features descriptor
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015507#comment-13015507 ]
Jean-Baptiste Onofré commented on KARAF-545:
--------------------------------------------
I'm gonna attach an user case to reproduce this behavior.
> 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
[jira] [Commented] (KARAF-545) Config file creation and update from
features descriptor
Posted by "Achim Nierbeck (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032022#comment-13032022 ]
Achim Nierbeck commented on KARAF-545:
--------------------------------------
an alternative solution might be to use the configfile tag, wdyt?
> 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
[jira] [Commented] (KARAF-545) Config file creation and update from
features descriptor
Posted by "Ioannis Canellos (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015493#comment-13015493 ]
Ioannis Canellos commented on KARAF-545:
----------------------------------------
It may be, cause I am making extensive use of it and I never had issues so far.
> 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
[jira] [Updated] (KARAF-545) Config file creation and update from
features descriptor
Posted by "Christian Schneider (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider updated KARAF-545:
--------------------------------------
Fix Version/s: (was: 3.0.0)
> 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é
> Assignee: Jean-Baptiste Onofré
> Fix For: 3.1.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.
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] [Commented] (KARAF-545) Config file creation and update from
features descriptor
Posted by "Ioannis Canellos (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051969#comment-13051969 ]
Ioannis Canellos commented on KARAF-545:
----------------------------------------
I think that the problem is that if the file does not exist, then it is not getting created. If it exists its properly updated.
> 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