Question

I have a product definition that includes one feature I wrote and the org.eclipse.feature. When I build this product from eclipse, it completes successfully. However, when I try to use the Headless build, the compilation process fails as it complains that it cannot find classes included in org.eclipse.ui. One of these classes, for example, is PlatformUI. The build process thus fails.

I’ve checked and the org.eclipse.ui is included in the org.eclipse.ui plugin. I’ve also tried to include this plugin explicitly in my custom feature, but to no avail.

I’ve also tried removing one of these plugins with problems, but the next that used org.eclipse.ui failed. So it seems to be definitively a classpath issue of some sowrt.

I’ve tried this headless build using version 3.3.2 of Eclipse.

Answer 1

The org.eclipse.ui.PlatformUI class is in the org.eclipse.ui.workbench plug-in.

org.eclipse.ui.workbench is required and re-exported by org.eclipse.ui.
The “org.eclipse.ui” package is a split package.

If you are using Import-Package for this dependency, then you are only getting wired to one of the providers of the package. If you only need the classes from the ui.workbench, then you can add an attribute to your Import-Package statement:

Import-Package:org.eclipse.ui;ui.workbench=split

Or, you could just change to Require-Bundle