Summary: | [Import/Export] Import existing projects into workspace - fails silently if there is a name collision | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Jens Seidel <jensseidel> |
Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | jensseidel, prakash |
Version: | 3.3 | Keywords: | helpwanted |
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: |
Description
Jens Seidel
2008-02-06 11:39:19 EST
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. 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. |