On 13.6.13 11:19, Jukka Zitting wrote:
Hi,
On Thu, Jun 13, 2013 at 1:13 PM, Michael Dürig <[email protected]> wrote:
Right. I guess we need to weight not having the stack trace at all since the
default logging configuration doesn't includes it against being able to
include additional information through configuration.
Which default configuration are you referring to? Can we change it?
A logging configuration that doesn't include the exception attached
with a warning log message seems potentially troublesome in any case.
Ok agreed. We make it the responsibility of the deployment to have a
"sensible" logging configuration then. I'll change this later on.
Michael
