Community
Participate
Working Groups
Suggestion: make the dependency visualizer flexible enough to also handle dependencies between plain Java projects (based on JDT model) or even between projects in general (based on resources model). In other words, make dependency visualization stand on its own and allow people to extend it to support arbitrary source models, instead of tying it all together.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.