Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 323470 - [WorkbenchLauncher] Could not launch because associated workspace is in use
Summary: [WorkbenchLauncher] Could not launch because associated workspace is in use
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.6.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact: Prakash Rangaraj CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-24 05:24 EDT by Lars Vogel CLA
Modified: 2010-12-02 05:23 EST (History)
5 users (show)

See Also:


Attachments
Screenshot (24.34 KB, image/png)
2010-08-24 05:25 EDT, Lars Vogel CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Vogel CLA 2010-08-24 05:24:52 EDT
During start of Eclipse I can select a default workspace.

If I select the flag "use this workspace as default" the system does not allow me to select another workspace if the default on is in use. It brings a message (screenshot attached) and cancels.

I think it would be nicer if the system would allow me to pick another workspace if the default one is in use.
Comment 1 Lars Vogel CLA 2010-08-24 05:25:29 EDT
Created attachment 177292 [details]
Screenshot
Comment 2 Prakash Rangaraj CLA 2010-08-24 05:33:47 EDT
Lars,

   What happens when you click OK in the dialog? For me it returns back to the Choose Workspace dialog.
Comment 3 Lars Vogel CLA 2010-08-24 05:36:33 EDT
If I press Ok Eclipse is closed.
Comment 4 Lars Vogel CLA 2010-11-29 14:45:54 EST
I believe I have found the reason why my behavior is different from Prakashs. I specified the -data "C:\Users\vogella\workspace\examples" parameter. It seems that if this parameter is specified and the workspace is used, you cannot change it.
Comment 5 Prakash Rangaraj CLA 2010-12-01 05:10:13 EST
(In reply to comment #4)
> I believe I have found the reason why my behavior is different from Prakashs. I
> specified the -data "C:\Users\vogella\workspace\examples" parameter. It seems
> that if this parameter is specified and the workspace is used, you cannot
> change it.

    May be because in that case, the OSGi data location is already set, so we can't/shouldn't be changing it.

Paul/Boris, 
    Any idea of the behaviour?
Comment 6 Boris Bokowski CLA 2010-12-01 11:52:25 EST
(In reply to comment #5)
>     May be because in that case, the OSGi data location is already set, so we
> can't/shouldn't be changing it.

Yes, the instance location will already be set before we (the IDE application) get a say in the matter, so the only thing we could do is restart (but then the -data command line arg will be there again). I don't think this can be fixed.
Comment 7 Lars Vogel CLA 2010-12-02 05:23:45 EST
Ok for me. At least I know now the reason.