Our team is developing an Eclipse RCP application that uses Spring DM to manage dependency injection. One of the issue we have is performance, where Spring DM extender tries to scan a large number of bundles during startup (about 100+ bundles need to be activated initially). Out of 400 bundles in our Eclipse RCP application, we only enable few bundles with Spring. I wonder if this is possible to configure the extender, so that most of the Eclipse bundles don't get scan by the extender during startup? Thank you for your attention.