The issue concerns navigating to function definition.
In the case of the sets of projects with complex dependencies to each other (such as Open Solaris), finding function
definition becomes a nontrivial task. Now the required projects are searched for definitions, but it is insufficient.
An infrastructure should be implemented that allows registering definitions and project dependencies. It then can be
implemented as a separate module.
Sorry, there is a typo in the description:
> An infrastructure should be implemented
> An infrastructure should be *introduced*
So this issue concerns the creation of the appropriate SPI, which can be implemented later on.
Do not forget that one service SPI already exists:
and is used in class view and h6yperlink in "Go To Declaration" actions.