Allow forcing the backtrace to print in ExceptionToTextProcessor + a fix: remove the redundant message that gets printed when including the backtrace. The processor printed the message + the stack trace, but the stack trace includes the messages of all exceptions, so it's redundant. We could also always use the result of
getMessageAndWholeBacktrace(), but I didn't want to change that much code for a small change.
I remember, that was to keep it backwards compatible w/ some uses, probably fatal error reporting. I'll take a look.
Can't see an array ever being used w/ this method, so I'm just going to change it and see if any tests fail. Worst case, the message may get printed out twice in some rare circumstances, so I think it's ok.