[
https://issues.apache.org/jira/browse/LOG4J2-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752185#comment-13752185
]
Tibor Benke commented on LOG4J2-374:
------------------------------------
I thought about it and I think we should use another pattern name than
%throwable in this case, because this improvement would imply the use of
%throwable{short} form, so it would be specious. Maybe the
DetailedShortThrowablePatternConverter or CustomShortThrowablePatternConverter
would be more expressive, so we could use the %dsThrowable or %csThrowable
names.
> Add more options to PatternLayout to display more detailed information about
> a Throwable
> ----------------------------------------------------------------------------------------
>
> Key: LOG4J2-374
> URL: https://issues.apache.org/jira/browse/LOG4J2-374
> Project: Log4j 2
> Issue Type: Improvement
> Components: Layouts
> Affects Versions: 2.0-beta9
> Reporter: Tibor Benke
>
> That would be useful if we got more details about the method which threw the
> exception. There is a "short" form, which contains these information, but
> there can be some cases, when we need them separately.
> For example we would write something like this:
> {noformat}
> %throwable{className}.%throwable{methodName}:%throwable{lineNumber}
> %throwable{message}
> {noformat}
> And we would get this:
> {noformat}
> foo.bar.ClassName.main:14 java.lang.ArithmeticException: / by zero
> {noformat}
> I think we should only modify the ThrowablePatternConverter and
> ThrowableFormatOptions classes and the documentation. What do you think about
> it?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
