Glad you're enjoying the new features! Hopefully it's not too much of a roller-coaster ride. ;-)
The problem is a so-called "dropped optional". If any of a bundle's optional package imports cannot be satisfied when the bundle is resolved, the unsatisfiable imports are discarded and then the bundle is not wired to the corresponding packages.
A (n optional) package import is unsatisfiable when either there is no export matching the import or when there are one or more exports that match the import, but wiring to any one of them would cause the importing bundle to fail to resolve because of a uses constraint violation.
You are observing a dropped optional package import because there is no export matching the import when the importing bundle is resolved.
The potential solutions to this are:
- ensure the exporting bundle is present in the repository before it is needed,
- refresh the bundle(s) with the dropped optional so the optional import becomes wired,
- automatic cloning.
Automatic cloning should happen in this case and I'm not sure why it isn't. The most obvious cause is that one or more uses constraints are missing (or possibly wrong). Or maybe the uses constraint isn't being violated because distinct bundles of your application are importing spring and hibernate. In the latter case, there may be missing uses constraints in your application.
If you could give a bit more detail, I can help you figure out what to try next.