karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johannes Utzig (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-5326) variables in cfg files are expanded
Date Mon, 04 Sep 2017 19:33:00 GMT

    [ https://issues.apache.org/jira/browse/KARAF-5326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152890#comment-16152890
] 

Johannes Utzig commented on KARAF-5326:
---------------------------------------

> It could be related to a Felix FileInstall change we did.

It appears that way. We downgraded fileinstall and produced a local build and the issue went
away.

> 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
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 4.2.0, 4.0.10, 4.1.3
>
>
> 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)

Mime
View raw message