Return-Path: X-Original-To: apmail-celix-commits-archive@www.apache.org Delivered-To: apmail-celix-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8B12411A6F for ; Wed, 13 Aug 2014 11:27:13 +0000 (UTC) Received: (qmail 2092 invoked by uid 500); 13 Aug 2014 11:27:12 -0000 Delivered-To: apmail-celix-commits-archive@celix.apache.org Received: (qmail 2004 invoked by uid 500); 13 Aug 2014 11:27:12 -0000 Mailing-List: contact commits-help@celix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@celix.apache.org Delivered-To: mailing list commits@celix.apache.org Received: (qmail 1871 invoked by uid 500); 13 Aug 2014 11:27:12 -0000 Delivered-To: apmail-incubator-celix-commits@incubator.apache.org Received: (qmail 1833 invoked by uid 99); 13 Aug 2014 11:27:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Aug 2014 11:27:12 +0000 Date: Wed, 13 Aug 2014 11:27:12 +0000 (UTC) From: "J.W. Janssen (JIRA)" To: celix-commits@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CELIX-138) Parameterise launcher MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CELIX-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.W. Janssen updated CELIX-138: ------------------------------- Attachment: 0001-Allow-launcher-to-use-different-configuration.patch Some additional fixes in the proposed solution of the previous patch... > Parameterise launcher > --------------------- > > Key: CELIX-138 > URL: https://issues.apache.org/jira/browse/CELIX-138 > Project: Celix > Issue Type: Improvement > Components: Framework > Reporter: J.W. Janssen > Attachments: 0001-Allow-launcher-to-use-different-configuration.patch, 0001-Allow-launcher-to-use-different-configuration.patch > > > The launcher currently always assumes its configuration is located in the current working directory and named {{config.properties}}. Sometimes it comes in handy to give the launcher an explicit configuration in another location. > The launcher could take a single command-line argument that defines the location of the configuration file. If no argument is given, it could fall back to its default behaviour. -- This message was sent by Atlassian JIRA (v6.2#6252)