[
https://issues.apache.org/jira/browse/LOG4J2-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076557#comment-14076557
]
Ralph Goers edited comment on LOG4J2-744 at 7/28/14 6:38 PM:
-------------------------------------------------------------
It is listed right on the wiki home page for Logging.
http://wiki.apache.org/logging/Log4j2ReleaseGuide. However, there a couple of
items that need to be updated as there are some sub-projects that need to be
deleted from Nexus before releasing that aren't listed on the wiki.
was (Author: ralph.go...@dslextreme.com):
It is listed right on the wiki home page for Log4j 2.
http://wiki.apache.org/logging/Log4j2ReleaseGuide. However, there a couple of
items that need to be updated as there are some sub-projects that need to be
deleted from Nexus before releasing that aren't listed on the wiki.
> Avoid unnecessary Clock calls when TimestampMessage is logged
> -------------------------------------------------------------
>
> Key: LOG4J2-744
> URL: https://issues.apache.org/jira/browse/LOG4J2-744
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Scott Harrington
> Priority: Minor
> Attachments: LOG4J2-744-test.patch, LOG4J2-744.patch
>
>
> The TimestampMessage interface was introduced in LOG4J2-53 and revised for
> AsyncLogger in LOG4J2-455.
> I've observed that Clock.currentTimeMillis is still called which should not
> be necessary.
> I have two patches, one which adds JUnit tests that demonstrate the
> unnecessary Clock calls, and one which fixes the issue for both AsyncLogger
> and "traditional" configurations.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
