Bug 161350 - [WorkbenchLauncher] No error when workspace opened with c; or d; instead of c: or d:
Summary: [WorkbenchLauncher] No error when workspace opened with c; or d; instead of c...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-17 23:40 EDT by jkubasta CLA
Modified: 2019-09-06 16:04 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jkubasta CLA 2006-10-17 23:40:12 EDT 
I open a workspace called d;\smoketest
Workspace launches
errors encountered when using product as a result
would like error msg when drive is specified with semi-colon please
Comment 1 Steve Francisco CLA 2006-10-19 10:23:05 EDT 
Actually, a semicolon is a valid character in a directory name, so accidentally typing c;\smoketest instead of d:\smoketest isn't really different than accidentally typing c\smoketest.  They're all valid names.  

I would prefer if the workspace selection dialog gave a warning if a relative path is specified.  Saying "You specified a relative path for the workspace.  Are you sure you want to use <full-path>? <yes> <no> <cancel>" (and show the resulting absolute path that would be used based on the current working directory.
Comment 2 Boris Bokowski CLA 2007-01-02 11:15:22 EST 
Reassigning bugs to reflect changes in ownership.
Comment 3 Boris Bokowski CLA 2009-11-26 16:32:56 EST 
Prakash is now responsible for watching bugs in the [WorkbenchLauncher] component area.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:04:24 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.