Bug 276731 - [IDE] Opening referenced projects refers to workspace known projects only
Summary: [IDE] Opening referenced projects refers to workspace known projects only
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.4.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-18 11:21 EDT by Michael.Vogt 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 Michael.Vogt CLA 2009-05-18 11:21:40 EDT
Build ID: M20080911-1700

Steps To Reproduce:
1. Create three (general) projects, named test1, test2, test3 and have them open in the workspace.
2. In project properties of project test1, mark test2 and test3 as referenced projects.
3. Close all 3 projects test1, test2, and test3 using Navigator or Project Explorer.
4. Delete project test3 using Navigator or Project Explorer. Do not delete content. At this time you should see test1 and test2 as closed projects in your Navigator.
5. Open project test1.

The upcoming dialog box offers to open referenced projects. Clicking "Yes" will open test2 too. Unfortunately it will not open test3 although it is referenced by test1. Well, it can not open test3, because test3 is no longer known to the workspace. Instead of silently ignoring this case, I would expect another dialog to pop up, telling me that a referenced project (test3) could not be found in the workspace and is therefore not opened. Ideally the dialog would allow an easy navigation to the project import wizard to fix the problem.

I think this is a usability issue especially for the unexperienced user and it seems to be easy to fix. The issue is that the first dialog makes the user believe that all referenced projects are opened and there is no feedback about any problems.

More information:

This problem occurs in all Eclipse revisions I know of.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:11:50 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.