You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Michael Vorburger (JIRA)" <ji...@apache.org> on 2016/12/12 19:18:58 UTC
[jira] [Created] (FELIX-5448) Exception from bundle.start() should
be logged, not swallowed
Michael Vorburger created FELIX-5448:
----------------------------------------
Summary: Exception from bundle.start() should be logged, not swallowed
Key: FELIX-5448
URL: https://issues.apache.org/jira/browse/FELIX-5448
Project: Felix
Issue Type: Bug
Components: File Install
Affects Versions: fileinstall-3.5.4
Reporter: Michael Vorburger
based on http://stackoverflow.com/questions/41092687/how-to-see-why-bundle-requirements-are-not-fulfilled-in-apache-felix-log/ :
Isn't it a bug that File Install silently "swallows" (ignore, drops; does not log) any issues thrown when it (re)loads bundle and bundle.start() them?
Or are there valid use cases and reasons I'm missing why this "sinking" of bundle load errors may be intentional?
It's definitely a PITA to discover e.g. load issues by having to manually go into a Console, and lb and start - instead of just seeing them in the log.
Would a code contribution proposing a fix for this be welcome?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)