Hi,
yes, it's normal: the env variable support is now "implicit".
You can still use ${env:*} syntax (it's the explicit form), or just the
corresponding env variable is enough (implicit).
Basically, if you do:
export COM_MY_PID_FOO=bar
Karaf will set property foo to bar in etc/com.my.pid.cfg configuratuion
file (aka com.my.pid configuration).
You can find some details about this here:
https://nanthrax.blogspot.com/2020/11/what-new-in-apache-karaf-430_9.html
http://karaf.apache.org/manual/latest/#_environment_variables_system_properties
Regards
JB
On 7/16/21 11:46 AM, Steven Huypens wrote:
Hi all,
After upgrading to Karaf 4.3.2 the config file
org.apache.karaf.management.cfg seems to have changed unexpectedly. For
example
*rmiRegistryPort = ${env:ORG_APACHE_KARAF_MANAGEMENT_RMIREGISTRYPORT:-1099}*
has been changed into
*rmiRegistryPort = 1099*
Is this intentional ? From https://issues.apache.org/jira/browse/KARAF-4609
I understand the environment variables should be included in 4.3 as well ?
Kind regards,
Steven Huypens
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
