Unfortunately there are no OSGi APIs that can give you more detailed information on why a particular bundle cannot resolve. In Equinox we have additional APIs that can be used to capture resolution results when the resolver is run, but that would bind you to Equinox in order to capture that more detailed resolution information.
Aside from that you could install your own ResolverHook that pays attention to when a empty capability collection is passed to filterMatches. That would indicate that some requirement is attempting to be resolved but there are not capabilities available to resolve it. But you would have to ensure your resolver hook is the 'last' one called, which is not always possible. It also would have a framework implementation detail that would require the implementation to call all resolver hooks even when the capability collection is empty. I'm not sure that is mandated by the specification. Tom From: Martin Petzold <[email protected]> To: OSGi Developer Mail List <[email protected]> Date: 07/03/2014 07:47 AM Subject: [osgi-dev] Inspect the dependencies of a subsystem and the bundles (content) within a subsystem Sent by: [email protected] Dear developers, I have got a question about how to inspect the dependencies of a subsystem and the bundles (content) within a subsystem. Currently a subsystem (with wrapped content) is installed and in state RESOLVED. However, some of the bundles are not resolved. The log ERROR and Exception only tell me "unable to resolve bundled". How can I receive more information about not resolves package dependencies within this scoped subsystem and of the subsystem itself? As far as I see the PackageAdmin is deprecated and also only gives information about already resolved bundles. What about the WireAdmin? But Wires also only exist, if a package is connected, right? Thanks and best regards, Martin _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
