[
http://jira.qos.ch/browse/LBCLASSIC-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12382#action_12382
]
Nick Spacek commented on LBCLASSIC-325:
---------------------------------------
I like the idea, but I don't like the thought of cluttering the <pattern> with
it. Is there any other way we could place a filter on the text output by the
logger?
> Filtering out selected stack trace frames
> -----------------------------------------
>
> Key: LBCLASSIC-325
> URL: http://jira.qos.ch/browse/LBCLASSIC-325
> Project: logback-classic
> Issue Type: New Feature
> Components: appender, layout
> Reporter: Tomasz Nurkiewicz
> Assignee: Logback dev list
> Priority: Minor
>
> Many frameworks and libraries like Spring or EJB are introducing hundreds of
> synthetic method invocations (AOP, dynamic proxies, CGLIB-generated classes,
> etc.) They are irrelevant for most of the time and only cluttering the stack
> traces printed by Logback.
> It would be nice to have possibility to filter (possibly by providing a set
> of patterns in logback.xml) each stack trace line and skip selected ones.
> Similar feature is implemented in some IDEs, see:
> http://blogs.jetbrains.com/idea/2010/07/console-folding-customization.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/logback-dev
