DO NOT REPLY - Ant discards stack traces for random exceptions terminating a build

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=43
398>.
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=43398





------- Additional Comments From stevelapache.org  2007-09-17 03:49 -------
There's nothing to stop us using introspection to get the
stack trace on those
things where getCause() works. There's also getStackTrace(),
which I've used in
smartfrog to take a complete chained stack trace and turn it
into a serializable
chain with stack trace information still retained. Very
powerful, but not
something I'd want to use via introspection



-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=ema
il
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone
who is.

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeant.apache.org
For additional commands, e-mail: dev-helpant.apache.org