Community
Participate
Working Groups
Build ID: 3.3.1.1 Steps To Reproduce: Let me partely quote comment 1 of bug 177567 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=177567#c1): Importing existing projects into workspace doesn't work if a different project with the same name is already open, even if the directory names are different from each other. The problem is that such projects are not even displayed which is quite confusing. Since there are too many imports possible I always wonder whether I try the proper one. If one fails silently as described I just try the next importer. Since I use for my C++ project also Subversion I'm most of the time not sure whether I have to import a Subversion project, a C++ project, a general project or whatever. That's why it is very important to show proper diagnotics! I often create a copy of my checked out project to work on different bugs at the same time: cp -r MyProject MyProject.SomeOtherStuff The .project file is not changed this may but it works nevertheless great on the command line (svn, make, ...). Now I wanted to debug a problem in MyProject.SomeOtherStuff and tried to open the copy in Eclipse by importing it. But the copy is not recognized if my workspace contains (the closed) MyProject project. I assume the problem is that only the project name is compared with all opened ones and not the paths. (Yes, I know that I would probably get an error if I try to open a different project with the same name of an existing one. But this should be happen after recognizing MyProject.SomeOtherStuff as it is otherwise very confusing not to find a valid project in the copy. Eclipse could also provide a dialog to rename the project in this case. Similar bug already closed with WORKSFORME https://bugs.eclipse.org/bugs/show_bug.cgi?id=190104 More information:
Currently the UI guesses that the name of the project is the name which is stored in the .project file. Your argument is that the project name is really the name of the directory that contains the project. Since in your case you get into this state only when you manually go to the file-system and perform a copy on the directory structure, one could argue that it is more common of an occurrence for the directory name not to be related to the project name. (via the UI any user is able to create a new project and put it in the directory of their choice) Perhaps allowing project renames on import would be a feature request that solves your problem. Moving to Platform/UI for consideration.
Regarding renaming a project on import, it will be tough to present a simpler UI. Right now you can import multiple projects in one single operation thru the wizard. When you are importing multiple projects and if few of them have a name conflict with some projects in the workspace, it would be complicated to present those projects alone for renaming. The whole issue is because the copy operation is performed outside Eclipse. If you right click your project and do a Copy & Paste, you will get a dialog for a new name for the project. You can specify MyProject.SomeOtherStuff there and start working on your bug. When ever you prefer you can switch to the original project and start working there. All your svn, make, etc will work fine with both the projects.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
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.
