celix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ErjanAltena <...@git.apache.org>
Subject [GitHub] celix pull request #10: CELIX-379: Added LAUNCHER option to add_deploy comma...
Date Mon, 10 Oct 2016 14:25:18 GMT
GitHub user ErjanAltena opened a pull request:


    CELIX-379: Added LAUNCHER option to add_deploy command

    Added LAUNCHER option to the add_deploy command to be able to use an own implementation
of the launcher. if the launcher is a target, the full path to this target will be used. 
    If it is not a target the launcher name will be used as an external command.
    If it is not defined, the default "celix" will be used.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ErjanAltena/celix develop

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #10
commit fc96bc5ef42e83b6c7bb23dbdda9f1b647c24ffb
Author: Erjan Altena <erjan.altena@nl.thalesgroup.com>
Date:   2016-10-10T14:19:05Z

    CELIX-379: Added LAUNCHER option to add_deploy command


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message