title: When a bundle is programmatically started, should dependencies also be started?
body: <p>Here's the scenario:</p>
  
  <p>I have a bundle 'BundleA' installed and started in an OSGi container. A new version of BundleA is available. BundleA is provisioned using Felix Bundle Repository. The new version of BundleA declares a new package level requirement on a package from 'BundleB'.</p>
  
  <p>Before I update BundleA (using OBR's deploy()) I stop BundleA because I want all threads to stop running and the deactivator provides this ability.</p>
  
  <p>When I perform a deploy() on BundleA, BundleB is also installed, as expected.</p>
  
  <p>I then programmatically start() BundleA again, and BundleA starts. But BundleB is 'resolved', not 'active'. I <em>can</em> manually start BundleB and it works as expected.</p>
  
  <p>Is this expected, related to a way I am programmatically calling OSGi API, or did something go wrong?</p>