You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2013/11/18 18:27:22 UTC
[jira] [Resolved] (KARAF-2569) Introduce KARAF_ETC env variable
[ https://issues.apache.org/jira/browse/KARAF-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved KARAF-2569.
-----------------------------------------
Resolution: Fixed
> Introduce KARAF_ETC env variable
> --------------------------------
>
> Key: KARAF-2569
> URL: https://issues.apache.org/jira/browse/KARAF-2569
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.4.0, 3.0.0
>
>
> Currently, the location of the Karaf etc folder is "forced": $KARAF_BASE/etc.
> If an user wants to use a custom etc folder (let say /etc/karaf on Unix system), he has to use a symbolic link.
> It's not easy, and more over, it can be an issue for rpm/deb packaging.
> Using rpm/deb packages, it would be great to have:
> - KARAF_HOME in /opt/karaf or /var/lib/karaf
> - KARAF_BASE in /var/lib/karaf
> - KARAF_DATA in /var/cache/karaf
> - KARAF_ETC in /etc/karaf
--
This message was sent by Atlassian JIRA
(v6.1#6144)