Bug 165482 - [WorkbenchLauncher] No automatic workspace creation if path not found
Summary: [WorkbenchLauncher] No automatic workspace creation if path not found
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   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: 2006-11-22 12:32 EST by Michael Stather CLA
Modified: 2019-09-06 16:17 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Stather CLA 2006-11-22 12:32:09 EST
When the path to the workspace isn´t found (perhaps because I moved the workspace) eclipse should ask me what to do instead of creating a new blank workspace at that direction.
Comment 1 Jakub Jurkiewicz CLA 2007-02-06 07:53:49 EST
Yes, I agree with Michael. It may lead a user to confusion. When someone else had moved the workspace, user would be surprised that Eclipse opened the workspace (by crating new dictionary - but user don't know about this) and there wouldn't be any projects. 
There should be a dialog, which would state that there was no workspace found in given directory. It should also ask whether new workspace should be created or the user wants to point which workspace should be used (as it is when Eclipse is run for the first time).
Comment 2 DJ Houghton CLA 2007-06-21 11:36:52 EDT
The runtime creates/uses whatever workspace location is passed to us.

The workspace chooser dialog is owned by the UI team.

Moving for comment.
Comment 3 Boris Bokowski CLA 2009-11-26 16:33:39 EST
Prakash is now responsible for watching bugs in the [WorkbenchLauncher] component area.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:17:27 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.