Bug 311083 - [CommonNavigator] Add a view that shows project references
Summary: [CommonNavigator] Add a view that shows project references
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-29 14:21 EDT by Jon Barrilleaux CLA
Modified: 2019-09-06 16:11 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jon Barrilleaux CLA 2010-04-29 14:21:11 EDT
Build Identifier: M20100211-1343

Views that show the projects in a workspace, such as package explorer, should have an option to show project dependencies.  Such hierarchical information would be useful in finding and resolving project dependency cycles.  It would also be useful in designing the structure (workspace references) of a workspace.

Reproducible: Always
Comment 1 Francis Upton IV CLA 2010-04-29 14:31:22 EDT
Jon, nice to hear from you.

Can you say a little more about what you would expect this to look like?
Comment 2 Jon Barrilleaux CLA 2010-04-29 14:40:52 EDT
Yes, after being laid off because my RCP-based project was grossly behind schedule, I finally landed a new job.  So it goes.

I'm thinking that just seeing the tree structure of the project dependencies would be a start.  Under a given project in the explorer I would see a "projects" node (similar to the "library" node that appears now for JRE dependencies). Opening that node would show all the referenced projects (and opening those nodes would show their referenced projects, and so on).

Another approach would be a Workspace View, with the intent to show the structure of the workspace as a whole, instead of just the structure of each project in the workspace.

BTW: There is a Project View, but it seems to be redundant and of no use for this problem.
Comment 3 Remy Suen CLA 2010-04-29 23:19:19 EDT
(In reply to comment #0)
> It would
> also be useful in designing the structure (workspace references) of a
> workspace.

What exactly is a "workspace reference" in this context?

(In reply to comment #2)
> Another approach would be a Workspace View, with the intent to show the
> structure of the workspace as a whole, instead of just the structure of each
> project in the workspace.

A workspace holds projects. When you say "structure" I presume you don't mean file system structure.

> BTW: There is a Project View, but it seems to be redundant and of no use for
> this problem.

That's from JDT. I wouldn't concern myself over it.
Comment 4 Francis Upton IV CLA 2010-04-29 23:28:53 EDT
(In reply to comment #3)
.
> 
> What exactly is a "workspace reference" in this context?
I think he's talking about the Project References which I think is something maintained by resources. Go into the properties of a project and look at the Project References tab.
Comment 5 Jon Barrilleaux CLA 2010-04-30 01:09:07 EDT
(In reply to comment #4)

Francis is correct.

What I am suggesting is a "view" so that one can see the projects referenced by another project, as a tree. Back when I was doing RCP work I recall there was such a view for plugin references -- you could look up or down the plugin reference tree.  And, of course, there is such a view in the JDT, called the Type Hierarchy, which allows you to look up or down the class tree.  It's such a common paradigm in Eclipse for viewing hierarchical references I was really surprised when I couldn't find such a view for project references.


> (In reply to comment #3)
> .
> > 
> > What exactly is a "workspace reference" in this context?
> I think he's talking about the Project References which I think is something
> maintained by resources. Go into the properties of a project and look at the
> Project References tab.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:11:22 EDT
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.