Bug 278763 - [Wizards] Consequences of creating a project in already existing location are non-obvious
Summary: [Wizards] Consequences of creating a project in already existing location are...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-02 08:31 EDT by Jacek Pospychala CLA
Modified: 2019-09-06 16:06 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jacek Pospychala CLA 2009-06-02 08:31:51 EDT
Imagine following real scenario of a beginner user:
1. Launch Eclipse, e.g. from c:\eclipse\eclipse.exe
2. Create new project but use custom location: c:\eclipse
3. Project gets created and shows all original contents of c:\eclipse directory as it's own
4. Remove project - c:\eclipse is removed together with all original contents and simply breaks eclipse setup.

Yes it's silly scenario, but such things happen to beginners! :-)

How the UI could be improved to protect future users from that?
Would it be possible to show extra info for non-empty folders selected by user in the new project wizard? e.g "All contents of this folder will be included in the project"...?
Comment 1 Kevin McGuire CLA 2009-06-05 10:54:09 EDT
(In reply to comment #0)

> Would it be possible to show extra info for non-empty folders selected by user
> in the new project wizard? e.g "All contents of this folder will be included in
> the project"...?

Yes, that could be helpful. 

Comment 2 Boris Bokowski CLA 2009-11-26 16:21:17 EST
Prakash is now responsible for watching bugs in the [Wizards] component area.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:06:22 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.