You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2003/08/20 16:11:05 UTC
DO NOT REPLY [Bug 22589] New: -
Empty Output to File from Java Task if Java Fails
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22589>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22589
Empty Output to File from Java Task if Java Fails
Summary: Empty Output to File from Java Task if Java Fails
Product: Ant
Version: 1.5.4
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: Core tasks
AssignedTo: dev@ant.apache.org
ReportedBy: erico@sedonacorp.com
<java
classname="com.myclass.class"
fork="yes"
failonerror="true"
output="mylog.log"
>
I have a Java class that does a deployment task, sending large amounts of text
to stdout as it proceeds. This text is never looked at unless it is needed for
debugging when the Java class fails for a variety of possible reasons.
Consequently, I want to be able to log that output to a file and not bother with
it unless the Java class fails. Unfortunately, if the Java class fails, the log
file is empty.
When the output attribute is set, somehow all Java output should be flushed to
the file for capture prior to the build failure.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org