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. > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
