On May 22, 2010, at 8:13 PM, Curt Arnold wrote:
On May 22, 2010, at 10:50 AM, Ralph Goers wrote:
Also, I have had an issue where the I wanted the toString() method on the
object to be logged to be delayed as much as possible (somewhat helped with
the {}-construct in slf4j). This
https://issues.apache.org/bugzilla/show_bug.cgi?id=49329
Summary: Smart and compact formatting of package/class names.
Product: Log4j
Version: 1.2
Platform: PC
OS/Version: Windows Vista
Status: NEW
Severity: normal
https://issues.apache.org/bugzilla/show_bug.cgi?id=49329
--- Comment #1 from Ralph Goers ralph.go...@dslextreme.com 2010-05-23
14:47:02 EDT ---
Code to do this is in my Log4j 2.0 experimental branch. However, the code that
does it was part of enhancements to the PatternLayout that Curt Arnold
[
https://issues.apache.org/jira/browse/LOG4J2-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12870445#action_12870445
]
Ralph Goers commented on LOG4J2-12:
---
My experimental branch provides compatibility with
On May 23, 2010, at 2:27 AM, Ralph Goers wrote:
On May 22, 2010, at 8:13 PM, Curt Arnold wrote:
On May 22, 2010, at 10:50 AM, Ralph Goers wrote:
Also, I have had an issue where the I wanted the toString() method on the
object to be logged to be delayed as much as possible
I'm prepping to start diving into the recent code drop and trying to figure out
how to do so in an effective way. I was thinking maybe the best way to
approach it would be to use annotations or javadoc to make comments on the
classes or methods. This fairly old article
