Community
Participate
Working Groups
Build ID: I20080617-2000 Steps To Reproduce: We have a number of Eclipse application launchers that are used internally for tasks such as code generation (java jet for example) and that have always been running against the local workspace ({workspace_loc}). We have used those since the 3.1 days, but under 3.4 we get that error that "Could not launch the application because the associated workspace is currently in use by another Eclipse application". I supposed that this other application is my Eclipse instance, but launching an "application" rather than a "product" as always worked in the past. More information:
Chris, any idea what might be behind this?
This is probably due to PDE being smarter in how it checks for workspaces being in use. In the past, PDE was lenient in letting you launch against workspaces that were already locked... this caused problems for people. So in 3.4, we now query Equinox to see if a workspace is locked or not.
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
Prakash is now responsible for watching bugs in the [WorkbenchLauncher] component area.
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.
