You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@celix.apache.org by "Alexander Broekhuis (JIRA)" <ji...@apache.org> on 2014/08/13 13:33:11 UTC

[jira] [Resolved] (CELIX-138) Parameterise launcher

     [ https://issues.apache.org/jira/browse/CELIX-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Broekhuis resolved CELIX-138.
---------------------------------------

    Resolution: Fixed

Applied the patch. Please close if it is ok. Thanks for the work!

------------
Author: abroekhuis
Date: Wed Aug 13 11:30:47 2014
New Revision: 1617704

URL: http://svn.apache.org/r1617704
Log:
CELIX-138: Applied 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
>            Assignee: Alexander Broekhuis
>         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)