Minor Description
When using the Karaf commandline command 'diag' to diagnose a Spring-DM bundle, not all diagnostic information is provided.
For example, I have several Spring-DM enabled bundles which I wish to deploy in Karaf however often I do not have their Spring-dependencies available. This means the bundles go to the waiting state as can be seen with the 'list' command. As I am not the author of these bundles I need to discovery easily exactly what dependencies are currently unavailable.
Using the 'diag' command on the Spring-DM enabled bundles initially only states the bundle is 'waiting' but it does not state what dependency it is waiting for. I understand that this is a bug with Karaf 'diag' command, see link below.
Currently the only way to resolve the issue is to either inspect the Karaf logs for bundle startup or failure messages (which can be inconvenient if the logs are constantly updating as in my case) or inspect the bundle itself.
I can confirm I have the org.apache.karaf.bundle.springstate bundle installed. This issue was raised following this Stack Overflow post:
The issue can be re-created by deploying a Spring-DM enabled bundle into Karaf which has a dependency on another Spring-DM enabled bundle but which is NOT made available.