[
https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862012#comment-16862012
]
Carsten Ziegeler edited comment on SLING-8484 at 6/12/19 11:39 AM:
-------------------------------------------------------------------
I'm wondering if this works - I don't think framework.start() blocks until the
final start level is reached. What about lazy activated bundles?
The more I think about this, the less useful this option becomes as the
analyzer most likely will catch many of the things and for the ones not catched
by the analyer we have the system ready / health checks. If these are started
they can tell, whether everything is fine. If they don't start, you know this
by not getting a response as well.
So in summary, I think this is not needed at all and does not provide
additional value
was (Author: cziegeler):
I'm wondering if this works - I don't think framework.start() blocks until the
final start level is reached. What about lazy activated bundles?
The more I think about this, the less useful this option becomes as the
analyzer most likely will catch many of the things.
> 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)
