[KARAF-5326] variables in cfg files are expanded

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.1.2
• Fix Version/s: 4.1.3, 4.2.0.M1
• Component/s: karaf
• Assignee: Guillaume Nodet
• Reporter: Johannes Utzig
• Created: 29/Aug/17 13:38
• Updated: 13/Sep/18 19:00
• Resolved: 12/Sep/17 06:14

Description

When starting karaf 4.1.2 it automatically expands all variables in cfg files and stores the expanded value.
As an example, org.ops4j.pax.logging.cfg contains:

log4j2.appender.rolling.fileName = ${karaf.data}/log/karaf.log

After starting karaf this becomes

log4j2.appender.rolling.fileName = C:\\Users\\username\\Downloads\\apache-karaf-4.1.2\\apache-karaf-4.1.2
data/log/karaf.log

The same worked fine with karaf 4.1.1, there the variables stay variables even if the file is manually modified.

Issue Links

• depends upon: FELIX-5688 TypedProperties#put method is not idempotent
• depends upon: FELIX-5689 FileInstall always expand configuration files
• depends upon: KARAF-5358 Upgrade to Felix Utils 1.10.2 and FileInstall 3.6.2
• is duplicated by: KARAF-5444 Unable to use Log4j2 ContextMapLookup with pax-logging
• is related to: FELIX-5642 string configurations in *.config files breaking behaviour change in 3.6.0
• links to: Introduced by