[
https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862104#comment-16862104
]
Carsten Ziegeler commented on SLING-8484:
-----------------------------------------
I wouldn't recommend launching anything without running the analyzer first.
This seems to be an anti pattern. If people are adventurous and want to launch
random stuff with the launcher, than I think its their problem.
As we see, there are only a few cases this extra code is catching and it would
need to be enhanced to not fail in all the scenarios already mentioned here
(lazy bundles, bundles in higher start levels)
A system ready check can easily fail fast in the situations that this addition
wants to catch. And in addition, the failing bundle might be one of the last
bundles that start anyway so the time until this additional code fails is
pretty close to the time the ready check would be available to call.
With this we're adding complexity without a strong use case that isn't already
solved by other means
> Fail the launcher if not all bundles could be launched
> ------------------------------------------------------
>
> Key: SLING-8484
> URL: https://issues.apache.org/jira/browse/SLING-8484
> Project: Sling
> Issue Type: Improvement
> Affects Versions: Feature Model Launcher 1.0.2
> Reporter: David Bosschaert
> Assignee: David Bosschaert
> Priority: Major
> Fix For: Feature Model Launcher 1.0.4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If the launcher is not able to start all bundles successfully, the launcher
> should fail with a non-zero exit code.
> This functionality should not be the default. It needs to be enabled with a
> flag, for example -foe (Fail on Error)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
