What happens if I have a set of <config> elements in my feature definitions, and two or more features include <config> values for the same "parameter". Will the resulting parameter value be arbitrary, i.e. it could be any of the specified values, or is there some deterministic way to know which value that gets set?
I would like to have a feature, that has some "deafult" settings and if another feature references this feature, it should also be able to include settings that overides some or all of the "defaults". Is there a solution to this within the current (2.2.9) functionality, that also will remain within future releases? Thanks Lars -- View this message in context: http://karaf.922171.n3.nabble.com/Same-configuration-elements-in-multiple-features-tp4025733.html Sent from the Karaf - User mailing list archive at Nabble.com.
