Return-Path: 
 <user-return-2242-apmail-karaf-user-archive=karaf.apache.org@karaf.apache.org>
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 4496B94E3
	for <apmail-karaf-user-archive@minotaur.apache.org>;
 Wed, 11 Jan 2012 19:37:18 +0000 (UTC)
Received: (qmail 36637 invoked by uid 500); 11 Jan 2012 19:37:18 -0000
Delivered-To: apmail-karaf-user-archive@karaf.apache.org
Received: (qmail 36570 invoked by uid 500); 11 Jan 2012 19:37:17 -0000
Mailing-List: contact user-help@karaf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@karaf.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@karaf.apache.org>
List-Post: <mailto:user@karaf.apache.org>
List-Id: <user.karaf.apache.org>
Reply-To: user@karaf.apache.org
Delivered-To: mailing list user@karaf.apache.org
Received: (qmail 36555 invoked by uid 99); 11 Jan 2012 19:37:17 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jan 2012 19:37:17 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of bengt.rodehav@gmail.com
 designates 209.85.214.176 as permitted sender)
Received: from [209.85.214.176] (HELO mail-tul01m020-f176.google.com)
 (209.85.214.176)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jan 2012 19:37:09 +0000
Received: by obbwd1 with SMTP id wd1so1937806obb.21
        for <user@karaf.apache.org>; Wed, 11 Jan 2012 11:36:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:sender:date:x-google-sender-auth:message-id:subject
         :from:to:content-type;
        bh=cwQHRVqk2elG5ab1T4htAo3YeCYEu5lsp2v6wCd5L0I=;
        b=YG70hl8GRkIsjXM9LCCmxw7u6cCRwu+/zl3jO2IGIgqSXjb4Lthmt9yXpzfY6SE3jk
         Jkwkl3ZrcGYIs3a+fhWqvXC+1L4U+3FyZf5t/fjNaquomqNOMD3xJ2/AbTVA64EJSwS6
         xqfvSr2kf208tFQYA4AxMFCXpGnuVCYtyoK5A=
MIME-Version: 1.0
Received: by 10.182.147.4 with SMTP id tg4mr427202obb.65.1326310608771; Wed,
 11 Jan 2012 11:36:48 -0800 (PST)
Sender: bengt.rodehav@gmail.com
Received: by 10.182.152.69 with HTTP; Wed, 11 Jan 2012 11:36:48 -0800 (PST)
Date: Wed, 11 Jan 2012 20:36:48 +0100
X-Google-Sender-Auth: g2CO8uoGTMeyxKp9fDSIjp45ncs
Message-ID: 
 <CAJ0TPG+pqt5WqiqhsSybsbovRfwBuGpQRFaNc4HE0aWKjjc=fQ@mail.gmail.com>
Subject: Using system properties in config.properties
From: Bengt Rodehav <bengt@rodehav.com>
To: user@karaf.apache.org
Content-Type: multipart/alternative; boundary=f46d04440066b298e304b645c07e
X-Virus-Checked: Checked by ClamAV on apache.org

--f46d04440066b298e304b645c07e
Content-Type: text/plain; charset=ISO-8859-1

I'm using Karaf 2.2.5 and the new possibility to specify ${optionals} in
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} =  ../../../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} =  ${commondir}/etc/custom.properties

Currently this is not possible. Can I create a JIRA for this or is there
another way I can accomplish this?

/Bengt

--f46d04440066b298e304b645c07e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I&#39;m using Karaf 2.2.5 and the new possibility to specify ${optionals} i=
n config.properties. It&#39;s a great functionality which allows our client=
s to optionally override the configuration that is part of our custom distr=
ibution.<div>
<br></div><div>I now have another request. Currently I have this line in my=
 config.properties:</div><div><br><div><div>${optionals} =3D =A0../../../co=
mmon/etc/custom.properties</div></div><div><br></div><div>This works in a f=
ixed directory hierarchy. I would like to be able to use system properties =
when definining the location of my custom.properties, like this:</div>
<div><br></div><div><div><div>${optionals} =3D =A0${commondir}/etc/custom.p=
roperties</div></div><div><br></div><div>Currently this is not possible. Ca=
n I create a JIRA for this or is there another way I can accomplish this?</=
div>
<div><br></div><div>/Bengt</div><br class=3D"Apple-interchange-newline"></d=
iv><div><br></div></div>

--f46d04440066b298e304b645c07e--