You can use the append attribute on feature config.
However, it won't override, it's only append. And it's the expected
behavior as if an user changes the properties, we don't want to override
the "custom" values.
Regards
JB
On 11/28/2016 05:11 PM, Tim Ward wrote:
OK, nearly there, thanks
Actually, feature now populate the etc folder as well (since
Karaf 4.0.5 AFAIR).
Regards
JB
On 11/28/2016 02:50 PM, Christian Schneider wrote:
You already found the confiFile option for features. This is the most
widely used option.
The alternative is the config option which simply adds the
Hi Tim,
as Christian already stated, you have two different ways of configuring.
1) inisde the feature itself as element
2) as external location, for example an URI to a resource located in a
Maven Repository. But here you can reference any valid URI pattern where a
corresponding URI handler is
2016-11-28 14:50 GMT+01:00 Christian Schneider :
> You already found the confiFile option for features. This is the most
> widely used option.
> The alternative is the config option which simply adds the config in
> config admin but not in etc.
>
Fwiw, both should add
On 28/11/2016 15:14, Christian Schneider wrote:
On 28.11.2016 15:14, Tim Ward wrote:
Thanks - replies inline:
On 28/11/2016 13:50, Christian Schneider wrote:
You already found the confiFile option for features. This is the
most widely used option.
So what is the "URL" in the element, and
On 28.11.2016 15:14, Tim Ward wrote:
Thanks - replies inline:
On 28/11/2016 13:50, Christian Schneider wrote:
You already found the confiFile option for features. This is the most
widely used option.
So what is the "URL" in the element, and how do my config
files get there from git?
The
Thanks - replies inline:
On 28/11/2016 13:50, Christian Schneider wrote:
You already found the confiFile option for features. This is the most
widely used option.
So what is the "URL" in the element, and how do my config
files get there from git?
The alternative is the config option which