Description Rafael Chaves 2003-03-12 12:37:05 EST

PDE Junit 2.1.4
Eclipse RC2

When launching a new Eclipse instance, the PDE JUnit plug-in includes plug-ins 
available in Eclipse SDK for each built-in plug-in that is not available in the 
current workspace. It should include only those available in the current 
workspace, or provide settings similar to PDE Run-time Workbench launch 
configuration, which allows including external plug-ins selectively.

Core has automated tests that will activate all plug-ins in the platform 
registry, and when running in headless mode (using 
org.eclipse.pde.junit.coretestapplication), this will create problems with UI-
oriented plug-ins (because the workbench is not properly initialized). Keeping 
only core-related plug-ins in the dev workspace won't work, because the 
launched Eclipse instance will include Eclipse SDK built-in installed plug-ins 
when they are not available in the dev workspace.

For instance, calling JUnitPlugin.initializeDefaultPluginPreferences will 
activate JDT UI, which will try to access the object returned by 
PlatformUI.getWorkbench(), which will be null.

The outcome is that some core automated tests won't work using a headless 
configuration even when the workspace has no UI-related plug-ins.