[
https://issues.apache.org/jira/browse/SLING-11442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564581#comment-17564581
]
Konrad Windszus edited comment on SLING-11442 at 7/9/22 1:54 PM:
-----------------------------------------------------------------
I would expect that if only goal {{start}} is called without subsequent
{{stop}} the feature keeps running by default (and is not coupled with the
Maven process). That should be standard and shouldn't require any flag. I don't
understand why this is needed:
https://github.com/apache/sling-feature-launcher-maven-plugin/blob/15236c7f4517d299e34335dba21bc99a09b65659/src/main/java/org/apache/sling/maven/feature/launcher/ProcessTracker.java#L52.
was (Author: kwin):
I would expect that if only goal {{start}} is called without subsequent
{{stop}} the feature keeps running by default (and is not coupled with the
Maven process). That should be standard and shouldn't require any flag.
> 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)
