Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to set up Eclipse PDE/Build with Indigo?
    primarykey
    data
    text
    <p>In my project I use PDE/Build to build my RCP application on a remote server in Hudson. The current version is a package based on Eclipse Galileo and it works fine both as a builder application and as a target platform. </p> <p>Now I want to upgrade it to Indigo and I need some help here.</p> <p>First, the old method of unpacking number of zips to form a target platform does not work. (I used Platform Runtime Binary, Delta pack, PDE Runtime Binary and JDT Runtime Binary - a set that I came up with that can be used both as a builder and as a target platform). </p> <p>Ok, there is new target definition for that. <strong>How would I configure it so that it corresponds to my Galileo set up?</strong> (And of course I wouldn't mind if it was simpler/cleaner).</p> <p>I tried the following:</p> <ol> <li>Added Eclipse RCP, Eclipse RCP Plug-in Developer Resources (for source), PDE/API Tools Environment from download.eclipse.org/eclipse/updates/3.7</li> <li>Added Eclipse Java Development from download.eclipse.org/releases/indigo</li> <li>Downloaded delta pack manually from download.eclipse.org/eclipse/downloads/drops/R-3.7-201106131736/download.php?dropFile=eclipse-3.7-delta-pack.zip, unpacked it and added the resulting directory (as Directory) to target definition. <strong>By the way, is there an update site for Indigo delta pack?</strong></li> <li>Added a couple of third party plug-ins from Eclipse Orbit p2 site: download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/repository</li> </ol> <p>I then used the definition's 'Set as Target Platform' - and my project builds fine in my workspace - that's nice! Then I exported the platform to . Now, if I try to execute my build like this:</p> <pre><code>java -jar &lt;target-platform&gt;\plugins\org.eclipse.equinox.launcher_1.2.0.v20110502.jar -application org.eclipse.ant.core.antRunner -buildfile &lt;target-platform&gt;/plugins/org.eclipse.pde.build_3.7.0.v20110512-1320/scripts/productBuild/productBuild.xml -Dbuilder=&lt;pdebuild-folder&gt; </code></pre> <p>or even</p> <pre><code>java -jar &lt;target-platform&gt;\plugins\org.eclipse.equinox.launcher_1.2.0.v20110502.jar </code></pre> <p><strong>I get the following error:</strong></p> <blockquote> <p>An error has occurred. See the log file \configuration\1316517334675.log</p> </blockquote> <p>The log contains the following:</p> <blockquote> <p>!SESSION 2011-09-20 15:15:34.269 eclipse.buildId=unknown java.version=1.7.0 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US</p> <p>!ENTRY org.eclipse.osgi 4 0 2011-09-20 15:15:35.175 !MESSAGE Application error !STACK 1 java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini). at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386)</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload