[jira] [Commented] (LOG4J2-1447) Garbage-free data structure for LogEvent's context map data

[ https://issues.apache.org/jira/browse/LOG4J2-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368980#comment-15368980 ] Remko Popma commented on LOG4J2-1447: - I am not quite sure how to proceed after Ralph

[jira] [Updated] (LOG4J2-1447) Garbage-free data structure for LogEvent's context map data

[ https://issues.apache.org/jira/browse/LOG4J2-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1447: Description: With each logging call, context map data is copied from the {{ThreadContext}} map int

[jira] [Commented] (LOG4J2-1447) Garbage-free data structure for LogEvent's context map data

[ https://issues.apache.org/jira/browse/LOG4J2-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368987#comment-15368987 ] Ralph Goers commented on LOG4J2-1447: - The only issue I have is with the put method.

[jira] [Comment Edited] (LOG4J2-1447) Garbage-free data structure for LogEvent's context map data

[ https://issues.apache.org/jira/browse/LOG4J2-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368987#comment-15368987 ] Ralph Goers edited comment on LOG4J2-1447 at 7/9/16 7:49 AM: -

[jira] [Commented] (LOG4J2-1447) Garbage-free data structure for LogEvent's context map data

[ https://issues.apache.org/jira/browse/LOG4J2-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368998#comment-15368998 ] Remko Popma commented on LOG4J2-1447: - Oh I see. Sure, we can move the mutator method

[jira] [Commented] (LOG4J2-1447) Garbage-free data structure for LogEvent's context map data

[ https://issues.apache.org/jira/browse/LOG4J2-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369128#comment-15369128 ] Ralph Goers commented on LOG4J2-1447: - Yes, that looks fine. > Garbage-free data str

Re: [VOTE] Log4j 2.6.2 rc1

+1 Ralph > On Jul 5, 2016, at 10:53 PM, Ralph Goers wrote: > > This is a vote to release Log4j 2.6.2, the next version of the Log4j 2 > project. > > Please download, test, and cast your votes on the log4j developers list. > [] +1, release the artifacts > [] -1, don't release because... > > T

[VOTE][RESULT] Log4j 2.6.2 rc1

The vote has passed with binding +1 votes from Mikael Ståldal, Matt Sicker, Gary Gregory, Remko Popma, and Ralph Goers. Leon Finker also voted +1. There were no other votes. Thanks to all who voted. I will be continuing the release process today. Ralph

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369313#comment-15369313 ] Gary Gregory commented on LOG4J2-1457: -- Hi Leon, Have you tried running all tests w

Logging web site

I have removed Log4j 1 from the main logging site and changed the title to just Log4j. The Log4j site has a link to Log4j 1. Log4j extras is still on the main site but should probably also be moved to the Legacy area of the Log4j site. Also, the Log4j site continues to say Log4j 2 predominant

Re: Logging web site

That all sounds good to me. Gary On Sat, Jul 9, 2016 at 10:13 PM, Ralph Goers wrote: > I have removed Log4j 1 from the main logging site and changed the title to > just Log4j. The Log4j site has a link to Log4j 1. Log4j extras is still > on the main site but should probably also be moved to t

Re: Log4j branding (was: Logging web site)

I agree very much with actions that make Log4j 2 more visible and accessible. It is important to consistently communicate the message that Log4j 1 is the old, legacy, End Of Life library and that we encourage everyone to move to Log4j 2. However, it would be a mistake to try to start rebranding Lo