Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316204 - [WorkbenchLauncher] Workspace path specified as only drive may restart in different workspace
Summary: [WorkbenchLauncher] Workspace path specified as only drive may restart in dif...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows All
: P3 normal with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-08 16:08 EDT by David Dubrow CLA
Modified: 2019-06-23 16:20 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 David Dubrow CLA 2010-06-08 16:08:34 EDT
The Workspace Launcher on Windows accepts only a drive specification in the Workspace field (e.g., "G:" as opposed to the path "G:\"). Although this defaults to the root of the drive when eclipse is first launched, it may silently change on restart. For example, if some plug-in changes the current working directory as part of its operation to "G:\Foo". On restart, even though the Workspace Launcher will display "G:" as the workspace location, "G:\Foo" will actually be used. This may look to the user like all her projects and workspace state disappeared.

A plain drive specification should be treated as the root of the drive by the Workspace Launcher.
Comment 1 Fabio Zadrozny CLA 2017-03-15 10:14:04 EDT
I've seen some users banging their heads against the wall because of this issue already ;)
Comment 2 Eclipse Genie CLA 2019-06-23 16:20:11 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.

--
The automated Eclipse Genie.