Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 356483 - [WorkspaceLauncher] Does not show, when auto-starting org.eclipse.debug.core bundle
Summary: [WorkspaceLauncher] Does not show, when auto-starting org.eclipse.debug.core ...
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-01 11:04 EDT by Frederic Gurr CLA
Modified: 2011-09-02 20:02 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frederic Gurr CLA 2011-09-01 11:04:23 EDT
Build Identifier: 20110615-0604

Originally we were trying to fix a problem with unnecessary context menu entries ("Run as..."/"Debug as...") in our RCP application. We found out that the org.eclipse.debug.core bundle needs to be loaded during start-up to make them go away (see also https://bugs.eclipse.org/bugs/show_bug.cgi?id=261545 as a reference, although this issue does not exactly relate to our problem).

Therefore we set the auto-start parameter of the org.eclipse.debug.core bundle to "true" in bundles.info of our application.

Then we started noticing that the dialog where you can choose you workspace (WorkspaceLauncher) during the first time launch did not show up anymore.
It was just skipped and the default workspace was used.

There were no error messages in the log file or the debug console.

Is this a specific problem of the org.eclipse.debug.core bundle being auto-started? Or a more general problem of the SimpleConfigurator?
(For example, auto-starting the org.eclipse.help bundle did not result in a missing WorkspaceLauncher dialog.)

Is there another (safe!) way of auto-starting the org.eclipse.debug.core bundle?

Reproducible: Always

Steps to Reproduce:
1. Extract a fresh Eclipse (eg. for RCP Development) copy into a folder
2. Open <EclipseRoot>\configuration\org.eclipse.equinox.simpleconfigurator\bundles.info
3. Change auto-start parameter of org.eclipse.debug.core to "true"
4. Save file
5. Start Eclipse
6. WorkspaceLauncher (aka the dialog that let's you choose the location of your workspace) is NOT shown
Comment 1 Frederic Gurr CLA 2011-09-01 11:06:47 EDT
This bug exists since (at least) Eclipse 3.5.
Comment 2 Remy Suen CLA 2011-09-01 11:33:31 EDT
Might be an eager initialization of the Location service.

Debug, you may want to reference bug 264698 for a similar problem that was encountered in the past.

Fred, please check who is setting 'osgi.instance.area' via FrameworkProperties's setProperty(String, String) method.
Comment 3 Pawel Piech CLA 2011-09-02 20:01:30 EDT
DebugPlugin.start() calls ResourcesPlugin.getWorkspace(), this will certainly force a workspace location to be set.

As an alternative you could force loading of the DebugPlugin with a call to DebugPlugin.getDefault() using the WorkbenchAdvisor (e.g. in post startup).  There may be other options as well.  

Please re-open bug if need be.
Comment 4 Pawel Piech CLA 2011-09-02 20:02:45 EDT
Perhaps invalid is a more accurate disposition, since we've never explicitly supported early startup for debug.