DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=35817>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=35817 ------- Additional Comments From [EMAIL PROTECTED] 2006-06-28 15:35 ------- (In reply to comment #4) > Unless you've actually looked at the source that's not a leap I would make. > > The javadoc tak is actually forking a new VM to run the javadoc tool, so it > can > very easily check the return status of the forked process to determine if it > "failed" or not. I'm not going to pretend to know how the task does what it does because, no, I haven't seen the code. But my leap wouldn't seem so far fetched. From what I can tell, both errors and warnings in javadoc are directed to stderr and one is ignored (warning) while the other is optionally reported. So I admit to making an assumption that something must be conditionally checking the stderr output for the error conditions if the user indicates failonerror. If not... well, this is how I would approach the task. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]