------- Additional Comments From mark at gcc dot gnu dot org 2005-03-17 10:30 ------- Note that I made it more verbose then it was in the past on purpose. But not for this case. See an example of a stacktrace were (most) of this "extra" information is useful: http://gcc.gnu.org/ml/java-patches/2005-q1/msg00337.html This really helps when debugging strange reasons for your main class not wanting to start correctly.
When cleaning this up be careful to at least keep the root cause and the classloaders and search paths used. And when the root cause is some (chained) ExceptionInInitializerError inside some super or interface class needed by the main class you really want the stacktrace to track down why/what happened where. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20508
