[
https://issues.apache.org/jira/browse/KARAF-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160210#comment-14160210
]
Achim Nierbeck commented on KARAF-3262:
---------------------------------------
Hmm, don't like the idea, I'd rather would like an approach where either a
${karaf.base} or ${karaf.etc} or ${karaf.data} can be used, where the default
and backward compatible way would be if no ${placeholder} is given it's
relative to karaf.base.
> Being able to use ${karaf.etc} in feature <configfile/> element
> ---------------------------------------------------------------
>
> Key: KARAF-3262
> URL: https://issues.apache.org/jira/browse/KARAF-3262
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.3, 2.4.1
>
>
> The <configfile/> element in a feature accepts a finalname attribute to
> define where the configfile has to be copied.
> However, finalname is relative to ${karaf.base}, whereas it should be able to
> use ${karaf.etc} (and so relative to ${karaf.etc}).
> In order to be backward compatible, if finalname starts with /etc/ it will be
> relative to ${karaf.base}, else it will be related to ${karaf.etc}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
