felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-5448) Exception from bundle.start() should be logged, not swallowed
Date Fri, 08 Sep 2017 07:53:00 GMT

    [ https://issues.apache.org/jira/browse/FELIX-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158264#comment-16158264

Guillaume Nodet commented on FELIX-5448:

It's supposed to be the case, but there's definitely a bug.

> 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
>             Fix For: fileinstall-3.6.2
> 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

View raw message