I am migrating my product based on 3.4.2 target platform from PDE Build to Buckminster. I am able to get this to work in a Galileo IDE with some trickery. However, this method does not work for the headless build and I am hoping someone has some ideas.
INFO: [start com.phurnace.deliver.feature:eclipse.feature$1.0.0#site.p2]
WARN: Missing executable launcher for configuration win32.win32.x86
WARN: Perhaps you should install the Platform Executable Launchers feature into your target platform
INFO: [end com.phurnace.deliver.feature:eclipse.feature$1.0.0#site.p2]
INFO: [start com.phurnace.deliver.feature:eclipse.feature$1.0.0#create.product]
[ant] /home/casey/buckminster/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
[ant] file:/home/casey/buckybuild/workspace/build/com.phurnace.deliver.feature_1.0.0-eclipse.feature/site.p2/
[ant] /home/casey/buckybuild/workspace/build/com.phurnace.deliver.feature_1.0.0-eclipse.feature/BLAppRelease.win32.win32.x86
[ant] The installable unit com.phurnace.deliver.ui.product has not been found.
[ant] Application failed, log file location: /home/casey/buckminster/configuration/1271187650185.log
ERROR: org.eclipse.core.runtime.CoreException: /home/casey/buckybuild/workspace/src/features/com.phurnace.deliver.feature/product.ant:22: Java returned: 13
org.eclipse.core.runtime.CoreException: /home/casey/buckybuild/workspace/src/features/com.phurnace.deliver.feature/product.ant:22: Java returned: 13
Ok, it looks like Buckminster site.p2 needs the Galileo executables feature in the target. I added *just* the executable launchers feature (from Galileo) to my target platform & was able execute the create.product action from the IDE. The product launches successfully!
Well, not so fast... When I try headless Buckminster, using same MSPEC, the director in create.product fails with:
[ant] /home/hudson/buckminster/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
[ant] file:/home/hudson/.hudson/jobs/deliver-build/workspace/build/com.phurnace.deliver.feature_1.0.0-eclipse.feature/site.p2/
[ant] /home/hudson/.hudson/jobs/deliver-build/workspace/build/com.phurnace.deliver.feature_1.0.0-eclipse.feature/BLAppRelease.win32.win32.x86
[ant] Cannot complete the install because of a conflicting dependency.
[ant] Software being installed: Deliver 1.0.0 (com.phurnace.deliver.ui.product 1.0.0)
[ant] Only one of the following can be installed at once:
[ant] Equinox Launcher Win32 X86 Fragment 1.0.101.R34x_v20080731 (org.eclipse.equinox.launcher.win32.win32.x86 1.0.101.R34x_v20080731)
[ant] Equinox Launcher Win32 X86 Fragment 1.0.200.v20090519 (org.eclipse.equinox.launcher.win32.win32.x86 1.0.200.v20090519)
[ant] Cannot satisfy dependency:
[ant] From: Deliver 1.0.0 (com.phurnace.deliver.ui.product 1.0.0)
[ant] To: org.eclipse.equinox.launcher.win32.win32.x86 [1.0.101.R34x_v20080731]
[ant] Cannot satisfy dependency:
[ant] From: Deliver 1.0.0 (com.phurnace.deliver.ui.product 1.0.0)
[ant] To: org.eclipse.equinox.launcher.win32.win32.x86 [1.0.200.v20090519]
[ant] Application failed, log file location: /home/hudson/buckminster/configuration/1271125335266.log
It seems like only p2 director is confused about dependencies here. It's not a problem when materializing or building. There must be a way to trick it into running in the same manner as in the IDE.
Unfortunately, I cannot migrate to a 3.5 platform quite yet, we have some unfortunate dependencies that still need migration.
Please help, I am so close to escaping the evil clutches of PDE Build!
Thanks!
Casey