[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=17568001#comment-17568001
]
Robert Munteanu commented on SLING-11442:
-
[~kwin] - I agree with your analysis, I am also not sure why I added all that
bookkeeping to the start goal. I've reverted my original changes in
https://github.com/apache/sling-feature-launcher-maven-plugin/pull/10 and will
look for a proper solution in a couple of weeks once I get back to this topic.
> 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)
[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=17564581#comment-17564581
]
Konrad Windszus commented on SLING-11442:
-
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)
[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=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)
