Thanks, I will take a look once the current releases are on vote.
Regards
JB
On 10/01/2022 00:53, Łukasz Dywicki wrote:
I made finally an issue for that improvement:
https://issues.apache.org/jira/browse/KARAF-7325
Took me a little bit longer than promised (C).
Leaving link at mailing list
I made finally an issue for that improvement:
https://issues.apache.org/jira/browse/KARAF-7325
Took me a little bit longer than promised (C).
Leaving link at mailing list for tracking purposes. ;-)
Best,
Łukasz
--
http://code-house.org
On 11.06.2021 12:25, Jean-Baptiste Onofre wrote:
Hi
It sounds good ! Thanks for the proposal. Let me know if you need help with
Jira, I will do the improvement.
Regards
JB
> Le 11 juin 2021 à 12:35, Łukasz Dywicki a écrit :
>
> Indeed It is the same mechanism I would love to see employed in
> mentioned places.
>
> The way how
Indeed It is the same mechanism I would love to see employed in
mentioned places.
The way how custom.system.properties works is great. Combined with
property resolver and fallbacks we can save peoples time in
synchronizing (jre|custom).properties.
I will try to book some time for this to
Hi Lukasz
It’s a good idea for system/custom properties. It’s similar/extend of the
custom.system.properties we already have in system.properties right ?
For json/cfg files, it’s not necessary as we can already override with system
properties or env variables (useful with docker) IMHO.
Hey all,
I recently been going over few Karaf assemblies I created in past years
and I realized that in many cases I had to copy entire configuration
shipped by Karaf distribution in order to include a new config in
bootstrap process.
Quite often my requirements were quite small, yet I had to
