[pde-build-dev] Migration to PDE Build 3.0 causes problems

[Chris Kelly <chrisk@xxxxxxxxxxxxx>]

I have recently moved from using PDE build to generate build scripts for
Eclipse 2.1.3 plugins to Eclipse 3 plugins. The PDE build for 2.1.3
successfully generates scripts for Eclipse 2.1.3 but for PDE Build 3.0.1
for Eclipse 3 I have run into a range of problems.

When generating scripts, I unzip a Eclipse SDK and create a virgin
installation. I also use a separate workspace directory when during the
script generation.


The following parameters when starting the antRunner to build scripts.
This eventually calls the genericTargets.xml file in
org.eclipse.pde.build_3.0.1 plugin.

The parameters are:

type=feature
id=com.enigmatec.ems.workbench-feature
buildDirectory=/home/chrisk/development2/branch/RIFBuild/build/RIFWorkbench/install
configInfo=linux,gtk,x86
baseLocation=/home/chrisk/development2/branch/RIFBuild/eclipseInstall/eclipse
buildingOSGi=true

For Eclipse 3.0.1, I get the following error when looking at the .log
file from my workspace.


!SESSION Dec 07, 2004 09:34:04.407
---------------------------------------------
eclipse.buildId=M200409161125
java.version=1.4.2_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=unknown, ARCH=x86, WS=unknown, NL=en_GB
Command-line arguments: -application org.eclipse.ant.core.antRunner -
buildfile /home/chrisk/development2/branch/RIFBuild/build/RIFWorkbench/createBuildScripts.xml 

....

!ENTRY org.eclipse.osgi Dec 07, 2004 09:34:04.407
!MESSAGE An unexpected runtime error has occurred.
!STACK 0
java.lang.NoClassDefFoundError: org/eclipse/swt/widgets/Listener
at org.eclipse.ui.plugin.AbstractUIPlugin.refreshPluginActions
(AbstractUIPlugin.java:804)
at org.eclipse.ui.plugin.AbstractUIPlugin$4.bundleChanged
(AbstractUIPlugin.java:918)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent
(BundleContextImpl.java:1151)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent
(EventManager.java:186)
at org.eclipse.osgi.framework.eventmgr.EventThread.run
(EventThread.java:104)

It doesn't matter if I put the swt libraries on the classpath and set up
the java.library.path to point to the .so files in the swt plugin. I
always get the same error.

I thought this  may be a bug so I've moved up to Eclipse 3.1M3 without
changes any parameters to start ant runner. This time I get a different
error. 


!SESSION 2004-12-07 07:22:23.598
-----------------------------------------------
eclipse.buildId=I200411050810
java.version=1.4.2_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=motif, NL=en_GB
Command-line arguments: -application org.eclipse.ant.core.antRunner -
buildfile /home/chrisk/development2/branch/RIFBuild/../RIFBuild/build/RIFWorkbench/createBuildScripts.xml 

...

!ENTRY org.eclipse.osgi 2004-12-07 07:22:23.599
!MESSAGE An error occured while automatically activating bundle
org.eclipse.ui.workbench (40).
!STACK 0
org.osgi.framework.BundleException: The activator
org.eclipse.ui.internal.WorkbenchPlugin for bundle
org.eclipse.ui.workbench is invalid
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:158)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start
(BundleContextImpl.java:933)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker
(BundleHost.java:421)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start
(AbstractBundle.java:293)
at org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass
(EclipseClassLoader.java:110)


I confused at how the BootLoader constants are worked out. I
specifically set the configuration to be linux,gtk,x86 but as you can
when using Eclipse 3.0.1, I get:
BootLoader constants: OS=unknown, ARCH=x86, WS=unknown, NL=en_GB

whereas for Eclipse 3.1M3 I get 
BootLoader constants: OS=linux, ARCH=x86, WS=motif, NL=en_GB


This is puzzling since I get ws=motif or unknown even though I'm
building on a linux box with gtk. Could this be causing problems?


Is this a bug as this automated build process was working prior to
moving to Eclipse 3?

Thanks for any help in advance.



-- 
Chris Kelly
Senior Software Engineer
Enigmatec Corporation
www.enigmatec.net