[
https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862007#comment-16862007
]
David Bosschaert edited comment on SLING-8484 at 6/12/19 11:21 AM:
-------------------------------------------------------------------
My initial implementation checks that after framework.start() is executed all
bundles are in the ACTIVE state.
If a bundle fails to resolve or throws an exception during start() this will be
prevented.
See here:
[https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/12/commits/cefcb9acbb59ceefbda1cf6b40421c5d544c208b#diff-799de4b49d1e99f3ee0bd1e2fec5b105R328]
Feedback appreciated :)
was (Author: bosschaert):
My initial implementation checks that after framework.start() is executed all
bundles are in the ACTIVE state.
See here:
[https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/12/commits/cefcb9acbb59ceefbda1cf6b40421c5d544c208b#diff-799de4b49d1e99f3ee0bd1e2fec5b105R328]
Feedback appreciated :)
> 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)
