Comments on: Getting started with PDE Build

By: Patrick

Patrick — Mon, 02 Aug 2010 22:12:00 +0000

Hi Johan,

Are you using Helios as your target platform or are you trying to build with Helios against a Galileo RCP target?

If you’re trying to build against a Helios target I have noticed some differences that required changes in the build script. I’ve been meaning to post these online, but I’ll email you the new sample projects.

— Patrick

By: Johan

Johan — Mon, 02 Aug 2010 08:31:59 +0000

Hi,

I’m using the PDE build script from your example but experiencing problems with Eclipse Helios that I did not encounter in Galileo. The problem manifests itself as false positives reported by the Hudson CI tool which used to call the Ant script in order to build code. Initially I thought this was a Hudson problem and documented the issue here: http://issues.hudson-ci.org/browse/HUDSON-6969. The resolution of that issue claims the problem is due to Ant errors not properly propagated, which I cannot understand since I’m only calling the one Ant target below:

Any ideas? Thankful for any thoughts about this.

By: Laurie

Laurie — Mon, 12 Jul 2010 18:09:49 +0000

Thank you for this sample of using PDE. I struggled with getting a build to work, researched the web for several days. I came across your example through one of my searches and had my build working in about 2-4 hours. I struggled with a few error messages. Today I figured it out by comparing what you had to what my build had. That was extremely helpful. I just wanted to say thanks for developing and sharing it so freely.

By: gambit

gambit — Thu, 01 Jul 2010 05:59:41 +0000

Thanks a lot. I am looking forward to test your example.
gambit

By: Patrick

Patrick — Wed, 30 Jun 2010 19:43:41 +0000

I think I know what’s going on here. Helios builds will require a slightly different setup because the RCP Runtime Binary is packaged as a p2 repository. I’m going to write a blog post soon with an updated example download. In the mean time, I’ll email you the example and if you could test it out, that would help me a lot.

Thanks,

— Patrick

By: gambit

gambit — Wed, 30 Jun 2010 14:03:49 +0000

Hi Patrick,

Very good tutorial. Unfortunately, for me your example does not work. It just doesn’t copy the launcher into the final archive. Everything else works. I am using the Eclipse Helios and I checked (several times now) any product parameter. I just cannot fix this one. Any ideas?
Thank your for the tutorial. It really helped me a lot so far.
gambit

By: Attila

Attila — Fri, 18 Jun 2010 23:02:06 +0000

Hi Patrick,

thank you very much for this tutorial.
After a half day frustration finally I found your description and it really worked!

Attila

By: Patrick

Patrick — Thu, 10 Jun 2010 20:40:47 +0000

Hi Diana,

First, it’s common to get a list of unsatisfied dependencies at the beginning of the build process. Unfortunately, these messages are a bit misleading and can usually be ignored. If one of the dependencies is actually a problem, the process will abort at that point.

It would help to know at exactly what point the build fails. Can you post the last few lines of output before you get the Java returned 13 message? Also, you can run Ant in verbose mode by passing the -verbose flag (you may have to pass it as -Dverbose) to the antRunner application when starting PDE Build. I generally haven’t found this to be very useful though.

— Patrick

By: diana

diana — Wed, 09 Jun 2010 09:09:41 +0000

Hi Patrick,

I have tried to switch a headless product-based build from eclipse 3.4.2 to eclipse 3.5.2
So, I have prepared a clean eclipse 3.5M2 + RCP SDK and de-archived inside it a suitable deltapack.
Further I have reused the build.properties from the previous build (from e3.4.2). Because the delta-pack shouldn’t be copied to eclipse/plugins dir, additionally, for the headless build on 3.5.2 I pass a property ${pluginPath} initialized with the path to the deltapack directory:

After triggering the build, everything seems fine, plugins start compiling…but in the middle of the process, build fails with Java returned: 13. (there are no compile errors because I have successfully exported the plugins from the build-directory in form of an executable!)
What I suspect is, that some plugin dependencies are not satisfied..
How can it be that while running the generateFeature and generateScript ant tasks, it outputs:
[java] [eclipse.generateFeature] Some inter-plug-in dependencies have not been satisfied.
[java] [eclipse.generateFeature] Host plug-in org.eclipse.core.net.win32.x86_0.0.0 has not been found.
[java] [eclipse.generateFeature] Bundle org.eclipse.core.net.win32.x86:
[java] [eclipse.generateFeature] Another singleton version selected: org.eclipse.core.net.win32.x86_1.0.0.I20080909
org.eclipse.equinox.launcher.win32.win32.x86.nl_de:
[java] [eclipse.generateFeature] Host plug-in org.eclipse.equinox.launcher.win32.win32.x86_0.0.0 has not been found.
These plugins are available in eclipse/plugins directory…
Where can I find a more verbose log file? The eclipse console output is not really saying anything.

Many thanks,
Diana.

By: Stefanko

Stefanko — Thu, 20 May 2010 13:31:27 +0000

Hi Patrick,

Thank you very much for your great help.

Best Regards,

Stefanko