You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Eric Norman (Jira)" <ji...@apache.org> on 2022/07/08 16:41:00 UTC

[jira] [Commented] (SLING-11442) Allow blocking after the features have been launched

    [ https://issues.apache.org/jira/browse/SLING-11442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564360#comment-17564360 ] 

Eric Norman commented on SLING-11442:
-------------------------------------

[~rombert] I believe this already possible with the changes that were done for SLING-10364 so isn't this a duplicate and redundant?

> Allow blocking after the features have been launched
> ----------------------------------------------------
>
>                 Key: SLING-11442
>                 URL: https://issues.apache.org/jira/browse/SLING-11442
>             Project: Sling
>          Issue Type: Improvement
>          Components: Maven Plugins and Archetypes
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>            Priority: Major
>             Fix For: Feature Launcher Maven Plugin 0.1.4
>
>
> The plug-in is right now working well in non-interactive scenarios, where one or multiple features are launched, tests executed, then the features stopped.
> It would be useful to configure the plug-in to block after the features have been started, e.g. by waiting indefinitely or waiting for user input. This way it could be used in an interactive manner to launch an application, e.g.
> {noformat}$ mvn clean package feature-launcher:start{noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)