Note that there are some explanatory texts on larger screens.

plurals
  1. POEclipse: starting custom eclipse app under linux returns to the command line prompt instantly
    primarykey
    data
    text
    <p>I am developing an Eclipse/Equinox based OSGI WebApplication (using embedded Jetty) and using headless PDE-Build for building the app. My build creates a zip file for Linux GTK and one for my local macosx.</p> <p>This has worked well so far and I could just unzip the linux zip file on my Debian based server and run <em>./eclipse</em> from the command line and the app would start up. </p> <p>Yesterday I had a new build ready and deployed it, unzipped it and started <em>./eclipse</em> and nothing happened. No output...nothing. It returned me the command line prompt immediately.</p> <pre><code>christoph@myserver:~/myapp$ ./eclipse christoph@myserver:~/myapp$ </code></pre> <p>What I have tried afterwards was starting manually with the equinox launcher:</p> <pre><code>christoph@myserver:~/myapp$ java -jar plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar </code></pre> <p>This looked much better and the application seemed to start as usual....but after about 10 seconds it stopped in the middle of startup and I was back at the command line prompt. </p> <p>Does anybody have an idea what could be the reason or how I can debug whats going on with the eclipse startup file? I think I haven't changed anything in the build scripts for weeks and the resulting zip file has the usual size what it was before. I also rebooted the server.</p> <p>I have tried things like <em>./eclipse -noexit</em>, <em>./eclipse -debug</em>, <em>./eclipse -clean</em> and <em>./eclipse -refresh</em> , <em>./eclipse -vm /path/to/my/jdk/java</em> but everything has the same effect. No output, nothing. </p> <p>Thanks Christoph</p>
    singulars
    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