Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 70581

Summary:

[WorkbenchLauncher] Incorrect message displayed when an invalid path is entered in Workspace Launcher Dialog.

Product:

[Eclipse Project] Platform

Reporter:

Sudarsha Wijenayake <sudarsha_wijenayake>

Component:

Assignee:

Platform UI Triaged <platform-ui-triaged>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

CC:

bso, Chris.Bailey, daniel_megert, eclipse, farrellp, jonathan.ball, steven.wasleski

Version:

3.0

Keywords:

helpwanted

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

stalebug

Bug Depends on:

67220

Bug Blocks:

Attachments:

Description	Flags
A screen capture of the error message	none

Description Sudarsha Wijenayake

2004-07-21 15:43:21 EDT

Problem Description: Incorrect message displayed when an invalid path is 
entered in the Workspace Launcher Dialog

You may complete the following steps to reproduce this scenario:
1. Launch Eclipse for the first time or delete the current workspace and 
configurations directory except “config.ini” file. Workspace Launcher Dialog 
is displayed. “<install location>\eclipse\workspace” is initially given in 
the “Workspace” field. 
2. Hit the Backspace Key to remove the default path and type “\\” in 
the “Workspace” filed.
3. Click on OK button. 
Expected Behavior: An error message is displayed stating that the provided 
path is invalid. 
Actual Behavior: The following message is displayed. 

“Workspace in use, choose a different one” 

A screen capture of the error message is attached to this defect

Comment 1 Sudarsha Wijenayake

2004-07-21 15:44:44 EDT

Created attachment 13502 [details]
A screen capture of the error message

Comment 2 Andrew Eidsness

2004-08-04 13:08:49 EDT

This is the result of the problem described by 67220.

Briefly, we use a single method (defined in the runtime) to set and lock the 
active workspace's instance area (since this must be done atomically).  The 
return code to this method is a simple boolean so there is no way of telling 
whether the operation failed because the instance area could not be set (e.g., 
the path is invalid) or because the lock failed (the area is already in use).

When bug 67220 is resolved we will have enough information to create a specific 
error message.

Comment 3 Andrew Eidsness

2004-09-07 12:10:14 EDT

*** Bug 72865 has been marked as a duplicate of this bug. ***

Comment 4 Andrew Eidsness

2004-09-14 08:37:54 EDT

*** Bug 73815 has been marked as a duplicate of this bug. ***

Comment 5 Andrew Eidsness

2004-09-29 12:11:45 EDT

*** Bug 75305 has been marked as a duplicate of this bug. ***

Comment 6 Michael Scharf

2006-07-23 22:44:00 EDT

Is there any chance for a resolution of this bug?

Comment 7 Boris Bokowski

2007-01-02 11:15:13 EST

Reassigning bugs to reflect changes in ownership.

Comment 8 Boris Bokowski

2009-11-26 16:32:28 EST

Prakash is now responsible for watching bugs in the [WorkbenchLauncher] component area.

Comment 9 Eclipse Webmaster

2019-09-06 16:13: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.

Comment 10 Eclipse Genie

2021-11-29 12:36:06 EST

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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.