codeconsole commented on PR #15564:
URL: https://github.com/apache/grails-core/pull/15564#issuecomment-4230251882
@jdaugherty there is no reason for 4 exceptions. 1 of which is obviously a
bug. I don't think adding `<logger name="StackTrace" level="OFF" />` to every
generated grails app is a good idea. It just adds confusion.
What about just adding a configuration to opt in the stack trace display?
The last change introduces:
```groovy
/**
* Whether the exception resolver should also emit the exception on the
separate
* {@code StackTrace} logger in addition to its own request-context log
entry.
* Defaults to {@code false}; set to {@code true} to restore the
historical two-logger
* behaviour, which allows routing the trace to a separate appender via
logback config.
*/
String SETTING_LOG_FULL_STACKTRACE =
'grails.exceptionresolver.logFullStackTrace'
```
so it is opt in instead of opt out.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
