Plug-in Builder

Tracker: Bugs

5 can't store stderr.txt when build process is failed. - ID: 2838403

Last Update: Comment added ( mbarchfe )

Details:

I recommend to set false on failonerror.I'll show you what I change the
value.
http://pluginbuilder.svn.sourceforge.net/viewvc/pluginbuilder/trunk/org.plu
ginbuilder.core/templates/initialProjectSetup/build.xml?view=markup
line:132 failonerror=true
Because if it fail on building, build process is finished.So it can't store
stderr.txt and I can't get infomation about why it is fail.

Submitted:

Hiroki Kondo ( kompiro ) - 2009-08-16 06:06

Priority:

Status:

Open

Resolution:

None

Assigned:

Nobody/Anonymous

Category:

None

Group:

None

Visibility:

Public

Comment ( 1 )

Date: 2009-08-19 06:27 Sender: mbarchfe thanks for the hint. However, are you sure that stderr.txt is not written if the build fails? I assumed that stderr.txt would contain the output to stderr independent of the return status of the java process. I also think that the Java process does not fail even if the PDE Build fails. That is because the antrunner does not seem to be able to change the return code of the Eclipse instance. So, the Java call only fails if the antrunner can not be invoked, e.g. because of a corrupt Eclipse instance. Therefore we look into stderr later and check for the occurrence of "Build failed". BTW, the best information for analyzing build errors is usually found in the workspace's log file (${buildDirectory}/workspace/.metadata/.log

Date: 2009-08-19 06:27
Sender: mbarchfe

thanks for the hint. However, are you sure that stderr.txt is not written
if the build fails? I assumed that stderr.txt would contain the output to
stderr independent of the return status of the java process.

I also think that the Java process does not fail even if the PDE Build
fails. That is because the antrunner does not seem to be able to change the
return code of the Eclipse instance. So, the Java call only fails if the
antrunner can not be invoked, e.g. because of a corrupt Eclipse instance.
Therefore we look into stderr later and check for the occurrence of "Build
failed".

BTW, the best information for analyzing build errors is usually found in
the workspace's log file (${buildDirectory}/workspace/.metadata/.log

Plug-in Builder

Tracker: Bugs

Comment ( 1 )

Log in to comment.

Attached File

No Files Currently Attached

Change

No changes have been made to this artifact.

About SourceForge

Find Software

Develop Software

Community

Help