Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 290440 - PDE JUnit launch configuration fails to launch
Summary: PDE JUnit launch configuration fails to launch
Status: CLOSED DUPLICATE of bug 286049
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-24 13:24 EDT by Michael Rennie CLA
Modified: 2010-04-09 09:59 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 Michael Rennie CLA 2009-09-24 13:24:58 EDT
I20090923-1538

Steps:

1. create a new plugin JUnit launch configuration for the debug test suite org.eclipse.jdt.debug.tests.AutomatedSuite
2. set the EE for the config to be 1.4, which is bound to a 1.4 JRE - in my tests using Sun 1.4 update 20
3. press run - tests run fine
4. kill the tests and open the launch dialog to the plugins tab
5. change the "Launch with" setting to 'plugins selected below'. Do not change any of the plugins, press save + run

Expected:

the tests would launch

Happens: 

org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException: No Classloader found for plug-in org.eclipse.jdt.debug.tests)
	at org.eclipse.swt.SWT.error(SWT.java:3955)
	at org.eclipse.swt.SWT.error(SWT.java:3870)
	at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:195)
	at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150)
	at org.eclipse.swt.widgets.Display.syncExec(Display.java:4317)
	at org.eclipse.ui.internal.testing.WorkbenchTestable.runTest(WorkbenchTestable.java:112)
	at org.eclipse.pde.internal.junit.runtime.UITestApplication.runTests(UITestApplication.java:114)
	at org.eclipse.ui.internal.testing.WorkbenchTestable$1.run(WorkbenchTestable.java:71)
	at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.IllegalArgumentException: No Classloader found for plug-in org.eclipse.jdt.debug.tests
	at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.getClassLoader(RemotePluginTestRunner.java:77)
	at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.getTestClassLoader(RemotePluginTestRunner.java:71)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.loadClass(RemoteTestRunner.java:693)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.loadClasses(RemoteTestRunner.java:429)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:452)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
	at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62)
	at org.eclipse.pde.internal.junit.runtime.UITestApplication$1.run(UITestApplication.java:116)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3860)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3481)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
	at org.eclipse.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:47)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:367)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:324)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:610)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:565)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1362)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1338)

I would expect the configuration to launch the same as it did before, since I have not changed anything except to say what to launch, which is the same in both cases.
Comment 1 Chris Aniszczyk CLA 2009-09-24 13:32:22 EDT
This could be related to the recent JDT Junit refactoring...
Comment 2 Markus Keller CLA 2010-04-09 09:59:50 EDT

*** This bug has been marked as a duplicate of bug 286049 ***