Summary: | [IDE] Open Referenced projects opens unpredictable list of projects | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Peter Braker <peter.braker> |
Component: | IDE | Assignee: | Platform UI Triaged <platform-ui-triaged> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | CWNL-Eclipse-Bugs, john.arthorne, paul.melching |
Version: | 3.2 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Peter Braker
2006-09-20 05:23:30 EDT
Does the set of projects that gets opened match the project references listed under Properties > Project References? I.e., I wonder if it is your project references that are not stable for some reason in your workspace. No: in the dialog "Project References" all checkboxes were empty, both when the project was open and after I closed it (for my "moftoolbase" project), while two projects were opened this time after selecting "Yes" from the dialog when opening "moftoolbase": "alturainfra" and "alturainfra.licensing", so not "alturainfra.projects". Probably easier to reproduce: I added EMF (Callisto 2.2.0 release) to my Eclipse 3.2 installation and proceeded with the first tutorial (http://dev.eclipse.org/viewcvs/indextools.cgi/*checkout*/org.eclipse.emf/doc/org.eclipse.emf.doc/tutorials/clibmod/clibmod.html). This results in 3 plugin projects: myEMFProject, myEMFProject.edit and myEMFProject.editor. The .editor plugin depends on the .edit plugin, which depends on the first plugin. When all 3 project are open, I close the .editor project first and then close the rest, then open the .editor project and answer "Yes", the other two projects are opened. OK. Then I close the myEMFProject project, then the .editor, and finally the .edit project. Open the .editor project, answer "Yes" and only the .edit project is opened. 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. |