Community
Participate
Working Groups
Using build I-20040304 I have a project (I'm using CDT projects) somewhere on file-system (eg C:\projects\MyProj), that I occasionally want to browse without touching. I also have a project with the same name "MyProj" in CVS. 1. Create a new (C++, Standard Make) project "MyProj" in a non-default location, C:\projects\MyProj. 2. After browsing, close the project. Forget to delete it. 3. From the CVS Repository Exploring perspective, find the project with the same name "MyProj". 4. Check out the project as a new project into the workspace: right-click > Check Out As... > The defaults are reasonable: Check out as a project in the workspace. The default project name is "MyProj". Next. The default location, in the workspace, is reasonable. Finish. 5. Eclipse detects that there already is a project by that name and you get a "Confirm Overwrite" dialog: The resource 'MyProj' already exists in the workspace and will be deleted. Proceed with the checkout of 'MyProj'? Oh right, I should have deleted the project back in step 2. It looks like this is going to do it for me though, so hit OK. 6. Start making changes to the project in Eclipse. These changes are happening in my workspace, right? That's where I specified them in step 4. WRONG. They are overwriting my uncontrolled project on disk. :-( EXPECTED: Do not overwrite the resources in step 5; instead delete them then recreate them. Alternatively, tell the user to delete the project in step 5 manually (with or without project contents).
I'm pretty sure we actually scrub the local project (e.g. delete deep without actually purging the project). This seems like user error, but we could of been more obvious how the closed project would be handled.
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.
