Bug 110342 - SWT Example Launcher: Double-click on "Standalone" folder produces a "Could not instantiate the class to run" log
Summary: SWT Example Launcher: Double-click on "Standalone" folder produces a "Could n...
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.1   Edit
Hardware: Sun Solaris-GTK
: P3 normal (vote)
Target Milestone: 3.1.2   Edit
Assignee: Carolyn MacLeod CLA Friend
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-22 12:09 EDT by Brian So CLA Friend
Modified: 2005-10-05 09:03 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brian So CLA Friend 2005-09-22 12:09:19 EDT
Build: Eclipse 3.1 I20050627-1435
Platform: Solaris GTK

Steps:
- Install Eclipse 3.1 with SWT Examples
- From Eclipse workbench, go to Window -> Show View -> Other ...
- Expand SWT Examples and select SWT Example Launcher. Click OK.
- From the SWT Example Launcher view, double-click the "Standalone" folder 
(under Examples) to open it.

The following error log is created:
!ENTRY org.eclipse.swt.examples.launcher 4 0 2005-09-22 12:00:56.675
!MESSAGE Could not instantiate the class to run.
!STACK 1
org.eclipse.core.runtime.CoreException: Executable extension definition 
for "mainClass" not found.
	at 
org.eclipse.core.internal.registry.ConfigurationElement.throwException
(ConfigurationElement.java:192)
	at 
org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtensio
n(ConfigurationElement.java:108)
	at 
org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableEx
tension(ConfigurationElementHandle.java:48)
	at org.eclipse.swt.examples.launcher.ItemDescriptor.createItemInstance
(ItemDescriptor.java:62)
	at org.eclipse.swt.examples.launcher.LauncherView.launchItem
(LauncherView.java:186)
	at org.eclipse.swt.examples.launcher.LauncherView.access$2
(LauncherView.java:169)
	at 
org.eclipse.swt.examples.launcher.LauncherView$1.widgetDefaultSelected
(LauncherView.java:69)
	at org.eclipse.swt.widgets.TypedListener.handleEvent
(TypedListener.java:97)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1021)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2867)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2572)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench
(Workbench.java:367)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
	at org.eclipse.ui.internal.ide.IDEApplication.run
(IDEApplication.java:103)
	at org.eclipse.core.internal.runtime.PlatformActivator$1.run
(PlatformActivator.java:226)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:376)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:163)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
	at org.eclipse.core.launcher.Main.run(Main.java:973)
	at org.eclipse.core.launcher.Main.main(Main.java:948)
!SUBENTRY 1 org.eclipse.core.runtime 4 1 2005-09-22 12:00:56.677
!MESSAGE Executable extension definition for "mainClass" not found.
Comment 1 Carolyn MacLeod CLA Friend 2005-10-03 16:30:21 EDT
Fixed > 20051003.

Released in HEAD for 3.2 stream.

For eclipse 3.1, the work-around is simply to use the +/- to expand/collapse 
the tree, instead of double-clicking on a category.

Steve to decide whether or not this (simple) fix should be back-ported to 
eclipse 3.1, seeing as how the examples are fairly visible.
Comment 2 Billy Biggs CLA Friend 2005-10-03 17:47:11 EDT
Marking for 3.2 M3 for now, anyway.
Comment 3 Steve Northover CLA Friend 2005-10-03 18:17:22 EDT
To be clear, it's a bug in the example, right?
Comment 4 Billy Biggs CLA Friend 2005-10-03 18:23:17 EDT
Yes.
Comment 5 Steve Northover CLA Friend 2005-10-03 18:34:17 EDT
Ok, put it in the 3.1.x stream.
Comment 6 Billy Biggs CLA Friend 2005-10-04 14:39:43 EDT
Done (there's no 3.1.2 target milestone yet in bugzilla, hope I remember to mark
this as such when there is).
Comment 7 Billy Biggs CLA Friend 2005-10-05 09:03:17 EDT
Marking 3.1.2.