Community
Participate
Working Groups
I20070313-1051 Launching Import.../Existing Projects into Workspace/Select root directory for a root directory that contains (amongst other directories): P w1/P where each P is a valid project, I get P twice in the project selection list without any clue about which is which. Found no option about this? The pain point is that you would then have to open one of them to guess who's who and then close it if it's not the one you want, remembering its rank in the list, then try the next one... (You cannot even open all of them and close the unwanted ones since the project names conflict.)
This happens to me as well even if my directory names are different from each other. Only the project names from .project is displayed (which do sometimes not differ) and no path. 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.
Guys, for me it looks like a duplicate of bug 35973. Am I right?
(In reply to comment #2) > Guys, for me it looks like a duplicate of bug 35973. Am I right? There are indeed many duplicates of this bug report open. I started already to add a comment to these (as I don't have the permission to mark a bug as duplicate) but I didn't matched all. Examples: 190104, 166149 and there are probably more Is there noone who wants to clean the database? Jens
This is a duplicate of bug 166149, thanks for pointing it out. This is not related to bug 190104 or bug 35973. *** This bug has been marked as a duplicate of bug 166149 ***
