Bug 213044 - [Preferences] Warning for new project reads in preferences from deleted project
Summary: [Preferences] Warning for new project reads in preferences from deleted project
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2.1   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-12-14 11:42 EST by Paul DiCarlo CLA
Modified: 2019-09-06 16:15 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul DiCarlo CLA 2007-12-14 11:42:13 EST
Build ID: 3.2.1

Steps To Reproduce:
Project settings are stored in the project folder. When a project is deleted w/o its content and you will try to add the project again (the same name), it will reuse the folder and the settings.  

The user may not realize that this is happening, and that they do not have the default settings one would normally associate with a clean new project.  (It could also be they want to get the same settings they had from the deleted project).

This is a request for a GUI enhancement: the users could be informed that the folder already exists and using it can have some (unpredictable) consequences e.g. some settings can be applied.  Perhaps also provide the option to blow away the existing directories.



More information:
I originally opened up defect #212950 in which I was told this was an intended behaviour (to use any settings in the directories which may exist).
Comment 1 DJ Houghton CLA 2007-12-18 10:22:12 EST
Tod, this is a UI request for confirmation when project contents already exist on disk.
Comment 2 Susan McCourt CLA 2009-07-09 19:29:40 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:15:47 EDT
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.