You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2017/02/28 07:23:45 UTC
[jira] [Closed] (SLING-6544) slingstart-maven-plugin:
keepLaunchpadRunning should be replaced by an option which can be used with
start and/or stop
[ https://issues.apache.org/jira/browse/SLING-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus closed SLING-6544.
----------------------------------
> slingstart-maven-plugin: keepLaunchpadRunning should be replaced by an option which can be used with start and/or stop
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-6544
> URL: https://issues.apache.org/jira/browse/SLING-6544
> Project: Sling
> Issue Type: Improvement
> Components: Tooling
> Affects Versions: Slingstart Maven Plugin 1.7.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Fix For: Slingstart Maven Plugin 1.7.2
>
>
> Right now the parameter {{keepLaunchpadRunning}} blocks the start mojo until one of the servers is terminated. It is not that easy to explicitly terminate the server though because Maven does not propagate the {{Ctrl+C}} to the server.
> Usually it is much more useful to instead block stopping of the server (i.e. the stop mojo).
> I would propose to deprecate {{keepLaunchpadRunning}} and instead introduce the following parameter (which may be used together with start and/or stop):
> {{blockUntilKeyIsPressed}} which should leverage the {{Prompter}} component (http://stackoverflow.com/a/21977269/5155923) which forces the Mojo to wait until the user entered some value.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)