[GitHub] [logging-log4net] fluffynuts commented on pull request #61: include source zip in release process

fluffynuts commented on pull request #61: URL: https://github.com/apache/logging-log4net/pull/61#issuecomment-662846390 Hi @SymbioticKilla Apologies for the delayed response -- I dropped the ball with a bunch of GH notifications recently 😞 As far as I'm aware, this PR does n

[GitHub] [logging-log4j2] rgoers commented on pull request #390: LOG4J2-2899: Fix log4j-1.2-api LogEventWrapper thread data accessors

rgoers commented on pull request #390: URL: https://github.com/apache/logging-log4j2/pull/390#issuecomment-662709377 Of course it can be guaranteed the original thread is around because most of the time the LogEventWrapper is called it will be from the same thread as the caller. Only when

[jira] [Work logged] (LOG4J2-2899) LogEventWrapper.getThread only works on the first invocation

[ https://issues.apache.org/jira/browse/LOG4J2-2899?focusedWorklogId=462268&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-462268 ] ASF GitHub Bot logged work on LOG4J2-2899: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] carterkozak commented on pull request #390: LOG4J2-2899: Fix log4j-1.2-api LogEventWrapper thread data accessors

carterkozak commented on pull request #390: URL: https://github.com/apache/logging-log4j2/pull/390#issuecomment-662432635 > I don't think it can be guaranteed that the methods will always be called on the same thread It can't be guaranteed that the original thread is still around or

[jira] [Work logged] (LOG4J2-2899) LogEventWrapper.getThread only works on the first invocation

[ https://issues.apache.org/jira/browse/LOG4J2-2899?focusedWorklogId=462040&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-462040 ] ASF GitHub Bot logged work on LOG4J2-2899: -- Author: ASF GitHub Bot