Hi,
if you use <confgfile/> instead of <config/>, you can use the override flag.
I think it makes sense to support override flag for the <config/> element as it
now creates the cfg file.
I will create a Jira about that.
Regards
JB
On 04/09/2017 10:25 PM, Achim Nierbeck wrote:
Hi Yogesh,
you only can append existing configurations, but not replace. [1]
This is by design, as already existing files can't be differentiate
between, already accustomed or needs to be "patched".
Regards, Achim
[1] -
https://github.com/apache/karaf/blob/master/features/core/src/main/resources/org/apache/karaf/features/karaf-features-1.4.0.xsd#L194
2017-04-08 19:29 GMT+02:00 yogu13 <[email protected]>:
Hi,
I noticed that the below configuration added as part of my custom feature
does not have any effect if etc/com.foo.bar.cfg has myProperty already
defined. I was hoping i could use the config to update a property which is
already defined and available
<config name="com.foo.bar">
myProperty = myValue
</config>
I stumbled across this scenario when i wanted to reset
aries.transaction.recoverable to false which is now turned on (set to true)
by default in karaf.
In case config updation is not supported by config tag can this support be
added ?
Let me know.. I can try and provide a PR
Regards,
-Yogesh
--
View this message in context: http://karaf.922171.n3.nabble.
com/Feature-configurations-do-not-update-existing-property-
as-part-of-etc-tp4050074.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
