| Workspace check [message #512161] |
Wed, 03 February 2010 23:22  |
Eclipse User |
|
|
|
Hi,
you all know that "Workspace cannot be locked" message appearing if you
attempt to start Eclipse twice with the same workspace.
Astonishingly I didn't notice this behaviour with my brand new RCP-based
product. I found out that the check is implemented by a set of !private!
methods in IDEApplication. checkInstanceLocation() is the method at the
top of them.
So the questions are:
Do I really need to protect the workspace?
If yes, is it the right way to just copy&paste the private methods from
IDEApplication to my own application class or is there a cleaner way?
Thanks and regards,
Dirk
|
|
|
| Re: Workspace check [message #518384 is a reply to message #512161] |
Wed, 03 March 2010 13:00  |
| Eclipse User |
|
|
|
Hi Dirk,
Do you need to protect the workspace?
--
Best Regards,
Wim Jongman
-- Smash forehead on keyboard to continue.....
(Eclipse Old Skool Quote Service)
> Hi,
>
> you all know that "Workspace cannot be locked" message appearing if you
> attempt to start Eclipse twice with the same workspace.
>
> Astonishingly I didn't notice this behaviour with my brand new RCP-based
> product. I found out that the check is implemented by a set of !private!
> methods in IDEApplication. checkInstanceLocation() is the method at the
> top of them.
>
> So the questions are:
>
> Do I really need to protect the workspace?
>
> If yes, is it the right way to just copy&paste the private methods from
> IDEApplication to my own application class or is there a cleaner way?
>
> Thanks and regards,
> Dirk
|
|
|
Powered by
FUDForum. Page generated in 1.13692 seconds
Home