Return-Path: X-Original-To: apmail-karaf-user-archive@minotaur.apache.org Delivered-To: apmail-karaf-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E2DE5B272 for ; Thu, 12 Jan 2012 07:06:59 +0000 (UTC) Received: (qmail 62249 invoked by uid 500); 12 Jan 2012 07:04:58 -0000 Delivered-To: apmail-karaf-user-archive@karaf.apache.org Received: (qmail 59519 invoked by uid 500); 12 Jan 2012 07:04:38 -0000 Mailing-List: contact user-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@karaf.apache.org Delivered-To: mailing list user@karaf.apache.org Received: (qmail 59472 invoked by uid 99); 12 Jan 2012 07:04:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jan 2012 07:04:34 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [217.70.183.195] (HELO relay3-d.mail.gandi.net) (217.70.183.195) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jan 2012 07:04:27 +0000 X-Originating-IP: 217.70.178.148 Received: from mfilter20-d.gandi.net (mfilter20-d.gandi.net [217.70.178.148]) by relay3-d.mail.gandi.net (Postfix) with ESMTP id B228BA8083 for ; Thu, 12 Jan 2012 08:04:06 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mfilter20-d.gandi.net Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by mfilter20-d.gandi.net (mfilter20-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id jMVJBTK3TKSL for ; Thu, 12 Jan 2012 08:04:05 +0100 (CET) X-Originating-IP: 80.214.0.64 Received: from [192.168.1.241] (unknown [80.214.0.64]) (Authenticated sender: jb@nanthrax.net) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id E03DCA8078 for ; Thu, 12 Jan 2012 08:04:04 +0100 (CET) Message-ID: <4F0E85DE.6040209@nanthrax.net> Date: Thu, 12 Jan 2012 08:03:58 +0100 From: =?ISO-8859-1?Q?Jean-Baptiste_Onofr=E9?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111124 Thunderbird/8.0 MIME-Version: 1.0 To: user@karaf.apache.org Subject: Re: Using system properties in config.properties References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Hi Bengt, you should be able to use ${karaf.home} and ${karaf.base} variables. Is it OK for you ? Regards JB On 01/11/2012 08:36 PM, Bengt Rodehav wrote: > I'm using Karaf 2.2.5 and the new possibility to specify ${optionals} i= n > config.properties. It's a great functionality which allows our clients > to optionally override the configuration that is part of our custom > distribution. > > I now have another request. Currently I have this line in my > config.properties: > > ${optionals} =3D ../../../common/etc/custom.properties > > This works in a fixed directory hierarchy. I would like to be able to > use system properties when definining the location of my > custom.properties, like this: > > ${optionals} =3D ${commondir}/etc/custom.properties > > Currently this is not possible. Can I create a JIRA for this or is ther= e > another way I can accomplish this? > > /Bengt > > --=20 Jean-Baptiste Onofr=E9 jbonofre@apache.org http://blog.nanthrax.net Talend - http://www.talend.com