The OSGi shell permits one to view what modules have been resolved at a
particular point in time. However, it is also important to know why a module
has been resolved. What module was it that triggered getting a module resolved?
This is a request to add diagnostic information to the system so that one can
find out why a module was resolved. Preferably, this would show the entire chain
of resolutions, starting with the explicit activation of a module, i.e., a
module that is in the Active state. For example, if module A is activated, and
it references module B which reference modules C which in turn references D, it
should be possible to execute some command or view some log output and see:
D <-- C <-- B <-- A
The inspect command in the OSGi shell does this to some extent. However, it is
not clear what the meanings of package, bundle, fragment and service are WRT an
OSGi module, and the dependencies as shown by that command appear to be
theoretical based on what is declared in the meta data rather than what actually
happened when a module was loaded.