in SLING-4226 encountered a strange bundle deployment problem in integration tests which I could reproduce with a few steps in launchpad and webconsole [1].
the generic steps are: 1. bundle B depends on exports of bundle A 2. bundle A is uninstalled - B is still running 3. bundle B can even be stopped/started, the dependencies to A still resolve although A is uninstalled and no longer visible in webconsole 4. after stopping/starting the launchpad/OSGi container B cannot be started due to missing dependency A - this is expected how it this possible? in what status is A after uninstalling? shouldn't be bundle B stopped automatically by OSGi when A is uninstalled, or at least when then bundle is restarted? stefan [1] https://issues.apache.org/jira/browse/SLING-4226?focusedCommentId=14246855#comment-14246855
