Description Ralf Ebert 2009-11-05 21:57:50 EST

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.4) Gecko/20091028 Ubuntu/9.10 (karmic) Firefox/3.5.4
Build Identifier: 3.5.1, 20090920-1017

- Headless tests run fine if one adds "org.eclipse.jdt.junit(4).runtime" and "org.eclipse.pde.junit.runtime" bundles to the run configuration. Why do you have to do that manually, couldn't the run configuration dialog know about that?

- Application "[No Application] Headless mode" for "JUnit Plug-in test" causes a warning about "org.eclipse.ui.ide" missing when you validate the plug-ins (you can ignore that, it's just confusing). "org.eclipse.ui.ide" is a bundle which is usually not included and not required for RCP target platforms. Why is that warning given?

- If you don't check "Run in UI thread" for a headless application (which pretty much makes no sense for a headless application, does it?), you get:

!ENTRY org.eclipse.osgi 4 0 2009-11-06 03:45:48.838
!MESSAGE Application error
!STACK 1
junit.framework.AssertionFailedError
	at junit.framework.Assert.fail(Assert.java:47)
	at junit.framework.Assert.assertTrue(Assert.java:20)
	at junit.framework.Assert.assertNotNull(Assert.java:217)
	at junit.framework.Assert.assertNotNull(Assert.java:210)
	at org.eclipse.pde.internal.junit.runtime.UITestApplication.getApplication(UITestApplication.java:70)
	at org.eclipse.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:38)
	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:368)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)


Reproducible: Always