ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 6323] New: - <javac> failonerror not working unless fork=true
Date Fri, 08 Feb 2002 08:20:07 GMT
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=6323>.
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=6323

<javac> failonerror not working unless fork=true

           Summary: <javac> failonerror not working unless fork=true
           Product: Ant
           Version: 1.5 alpha (nightly)
          Platform: Other
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Core tasks
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: steve_l@iseran.com


I dont have a standalone test case for this, it is late and I have to be up 
again in 6 hours time. Maybe I will ve time to code one tomorrow

<javac> does not seem to pick up System.exit() return codes unless fork=true. 
I have seen this in a standalone task, and it could explain why <jspc> aint 
picking up jsp compilation failure from jasper. But surely some other tasks 
would have noticed.

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message