Community
Participate
Working Groups
Build Identifier: I20100608-0911 I want to use headless build of some eclipse plugins inside of my main build process (based on make). A command like the following is used to start the headless build: /usr/bin/java -Djava.library.path=/usr/lib/jni:/usr/lib64:/usr/lib -jar $ECLIPSE_HOME/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar -application org.eclipse.ant.core.antRunner -buildfile $ECLIPSE_HOME/plugins/org.eclipse.pde.build_3.6.0.v20100603/scripts/build.xml -DbuildDirectory="$HOME/workspace/Project/build/java_build" -DbaseLocation="$ECLIPSE_HOME" If the build was successful, the java process exists with exit code=0 as expected. However whenever the build fails somewhere, the exit code is still zero. It seems that this bug was introduced in Helios first. With Galileo everything works just fine. Reproducible: Always Steps to Reproduce: 1. Prepare headless build 2. Insert syntax error into one java file 3. Run headless build and watch for the exit code of the java process.
Created attachment 175950 [details] Example for headless build Please import both projects into your workspace. Then edit the makefile variables and make sure, that the referenced jar files exist. After calling make you'll see, that Helios will always exit with error code 0 even if the compilation was not successful.
Works as expected when using nightly builds, e.g. I20100805-1700.
There really hasn't been any change in PDE/Build for 3.7 that I can imagine would affect this.
Possibly the problem is in one of the parts of eclipse which call the PDE like the equinox launcher, the antRunner application, etc. At least one component does not forward the event that the compile process was unsuccessful.
