Hello, Congratulations on this new release! Are there examples of how to configure LOGBACK-540 (filtering out selected stack trace frames), specifically using the LogBack API (not just from a configuration file)? I've looked at https://github.com/qos-ch/logback/commit/a71b2902cff5911bbb16d4e2950476b0dfe... and it's not particularly obvious how to add (and configure) ThrowableProxyConverter into a running application (the associated test case just shows how it is used with a specific event). For example, the following call in a Groovy application script (not talking about Groovy configuration): log.debug "message with ${interpolation}, in groovy code" ...will be logged as debug$call and not identify the script, because "debug" used in this way passes through Groovy's generated code, and that's what LogBack is recording. I'd like to be able to configure LogBack to filter out such "generated" code (this is just an example, we have other cases). Thanks, Christopher On 24 March 2015 at 13:10, Ceki Gülcü <ceki@qos.ch> wrote:

Hello all,

The logback team is happy to announce the release of logback version 1.1.3. It contains many bug fixes and improvements. It should hit the Maven central repository by the time you read this message.

Please refer to the news page for precise details about this release.

http://logback.qos.ch/news.html

You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL.

http://www.qos.ch/mailman/listinfo/announce

You may also receive announcements via twitter by following:

https://twitter.com/qos_ch

Enjoy, -- Ceki Gülcü _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user