[
https://issues.apache.org/jira/browse/LOG4J2-2639?focusedWorklogId=266946&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-266946
]
ASF GitHub Bot logged work on LOG4J2-2639:
------------------------------------------
Author: ASF GitHub Bot
Created on: 25/Jun/19 18:58
Start Date: 25/Jun/19 18:58
Worklog Time Spent: 10m
Work Description: rgoers commented on issue #284: LOG4J2-2639 - Allow
logging calls to be constructed using a builder pattern
URL: https://github.com/apache/logging-log4j2/pull/284#issuecomment-505577467
There should be no risk of a memory leak if log() is not called. The
LogBuilders are owned by a thread local. If log() is not called then the next
call to an "at" method would clear them for re-use. Even if one was dynamically
created it would be garbage collected as soon as the it went out of scope.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 266946)
Time Spent: 5.5h (was: 5h 20m)
> Allow log event to be created using the builder pattern.
> --------------------------------------------------------
>
> Key: LOG4J2-2639
> URL: https://issues.apache.org/jira/browse/LOG4J2-2639
> Project: Log4j 2
> Issue Type: Task
> Components: API
> Affects Versions: 3.0.0
> Reporter: Ralph Goers
> Priority: Major
> Time Spent: 5.5h
> Remaining Estimate: 0h
>
> In some cases it would be convenient to create log events using a builder
> pattern. One advantage of this approach is that it would allow the location
> information to be more easily provided.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
