The current format is more human readable, but the default format has the benefit that it can be understood by IDEs (IntelliJ, Eclipse), which can provide quick navigation to the relevant source.
We do the following in our exception stack traces:
Reconcile causes and try to present a unified trace
This might still be valuable.
Format this in a table
This is mainly what this issue is about.
Show the application stack trace
This currently doesn't work well and was mainly intended for XPL/XSLT. It would be nice if we could provide the user a better idea of what the application was trying to do beyond the Java stack trace. Separate issue.
The current format is more human readable, but the default format has the benefit that it can be understood by IDEs (IntelliJ, Eclipse), which can provide quick navigation to the relevant source.
+1 from user