[
https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862033#comment-16862033
]
David Bosschaert commented on SLING-8484:
-----------------------------------------
I could be wrong, but looking at the documentation of framework.start()
[https://osgi.org/javadoc/osgi.core/7.0.0/org/osgi/framework/launch/Framework.html#start--]
It indicates waiting until the FrameworkEvent.STARTED is fired which I think
only happens once the final start level has been reached.
But yes, lazy activated bundles are not caught that way, but at least we can
check that they were resolved (the current code doesn't do this yet).
I do agree that the Analyzer _should_ catch many of the problems, however I
think this would be a useful additional check for situations that might be
missed by the Analyzer...
> 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)
