You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Sascha Vogt (JIRA)" <ji...@apache.org> on 2017/08/30 15:58:00 UTC
[jira] [Commented] (KARAF-5326) variables in cfg files are expanded
[ https://issues.apache.org/jira/browse/KARAF-5326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16147498#comment-16147498 ]
Sascha Vogt commented on KARAF-5326:
------------------------------------
It looks like this was introduced with the updated to fileinstall 3.6.0 - downgrading to 3.5.8 and the variables remain as is
> variables in cfg files are expanded
> -----------------------------------
>
> Key: KARAF-5326
> URL: https://issues.apache.org/jira/browse/KARAF-5326
> Project: Karaf
> Issue Type: Bug
> Components: karaf-config
> Affects Versions: 4.1.2
> Reporter: Johannes Utzig
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)