You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2002/04/06 20:33:08 UTC

DO NOT REPLY [Bug 7800] New: - No error checking in java tasks in build.xml

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=7800>.
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=7800

No error checking in java tasks in build.xml

           Summary: No error checking in java tasks in build.xml
           Product: Xerces2-J
           Version: 2.0.1
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Other
        AssignedTo: xerces-j-dev@xml.apache.org
        ReportedBy: staschuk@telusplanet.net


The <java> tasks in build.xml do not set failonerror="yes",


so if the task fails, Ant quietly ignores it.





For example, if you try to build the docs in a chrooted


environment on my machine, it fails because it can't connect


to the X server.  An exception is thrown, the JVM exits


with return value 1, the docs remain unbuilt, but Ant thinks


all is well.

I can't think of a reason not to have failonerror="yes" on
all the forking <java> tasks.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org