Community
Participate
Working Groups
I have noticed an issue with the Project Copy dialog and found a second one while investigating the first. First, the very weird one: - Copy any project in your workspace with Ctrl+C - Ctrl+V it into your workspace - When the dialog pops up, uncheck Use default Location and type in any folder name in your existing workspace - Be greeted with an error dialog (see attached) no matter what folder name you specify I can't seem to get the above to work no matter what folder name I type in. It appears that this just always fails if you manually specify any folder *in your workspace directory*. I *can* copy the project if I specify a new folder outside my current workspace. As long as the new folder is a valid new folder I don't see why this should fail. I uncovered this trying to reproduce another bug our users reported - which I will file next. ;o)
Created attachment 50284 [details] Showing my copy dialog
Created attachment 50285 [details] Showing the error message
I assume you are using the final 3.2 build. I am only able to reproduce a failure when I select a location that does indeed overlap the location of another project (where overlap means the same as, or a parent of another project location). I would expect this to fail, although as I commented bug in bug 157507, the dialog should catch this and not allow ok to be pressed until a valid location is provided. I did notice that when I copied a project into a folder within another project, that the other project didn't properly refresh (this is in 3.3 HEAD). This is a bug in core resources - it is somehow not correctly updating aliases in this case.
Hi John, Yes - I am using Eclipse 3.2 final. That is weird - I am definitely seeing this error with both a non-existing folder in my current workspace, as well as an exisiting (empty) folder that I manually created outside of Eclipse in my current workspace. The only other difference I can think of is that I am running with a shared configuration area. But I can't see this having anything to do with it.
Created attachment 50305 [details] To prove I'm not insane Here's another screengrab showing my directory structure. Let me know if you need any other diagnostic info.
Can you clarify what you mean by "non-existing folder in my current workspace". Do you mean a folder within a project in your workspace, or just a directory that is a direct child of the workspace location? You are not allowed to copy a project into a folder that is a direct child of the workspace location, because that level is reserved for the default location of projects. I.e., if you want it to appear at that level, leave "Use default location" checked. I think the root of this problem is that the dialog is allowing you to proceed when you have chosen a location that we do not allow. On the other hand, you can use a location that is two levels below the workspace location if you want (below the default location for some other project). Sorry if this explanation is confusing...
I see from your latest screen shot that you are indeed using an invalid location. As I said in my previous comment, that location is reserved as the default location for a project with the name "_this_folder_doesnt_exist_" (even though such a project doesn't exist yet). On reflection I think there is room for improvement in the error message.
Yes, that's what I meant. Well, I guess this is admittedly a weird case. All I was trying to do was get the dialog to remember my choice of "not using a default location" so I could reproduce Bug #157507, and I didn't want to clutter my drive so I decided to just put it in the default location anyway (albeit manually). I'm fine with "don't do that", but I guess the error message is still a little unclear. Thanks for looking at this.
This bug is just about clarifying wording of the exception message.
Created attachment 78965 [details] The dialog in 3.3
Comment on attachment 78965 [details] The dialog in 3.3 I tested the issue using 3.3. Te dialog is already changed and the message more clear. Anyway I think there is still UI issue. If some locations are forbidden, we shouldn't be able to press OK in the Copy Project dialog. This is how it works in New Project wizard.
Comment on attachment 78965 [details] The dialog in 3.3 See bug 157507.
See comment #11 and #12.
