[jira] [Commented] (LOG4J2-1808) java.lang.NoSuchMethodError: org.apache.logging.log4j.ThreadContext.getThreadContextMap()

[ https://issues.apache.org/jira/browse/LOG4J2-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853014#comment-15853014 ] Matt Sicker commented on LOG4J2-1808: - This sort of thing could've been caught by the Provider API in

[jira] [Commented] (LOG4J2-1808) java.lang.NoSuchMethodError: org.apache.logging.log4j.ThreadContext.getThreadContextMap()

[ https://issues.apache.org/jira/browse/LOG4J2-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853001#comment-15853001 ] Remko Popma commented on LOG4J2-1808: - The method {{ThreadContext.getThreadContextMap()}} was added

[jira] [Created] (LOG4J2-1808) java.lang.NoSuchMethodError: org.apache.logging.log4j.ThreadContext.getThreadContextMap()

Lukasz Lenart created LOG4J2-1808: - Summary: java.lang.NoSuchMethodError: org.apache.logging.log4j.ThreadContext.getThreadContextMap() Key: LOG4J2-1808 URL: https://issues.apache.org/jira/browse/LOG4J2-1808

Re: SyslogAppender parameter name change

Thanks Matt! Sam, can you check if this resolves the issue? Sent from my iPhone > On Feb 4, 2017, at 14:49, Matt Sicker wrote: > > I see. There were a couple issues with @PluginAliases for SyslogAppender > specifically. Fixed in master. > >> On 3 February 2017 at 10:23,

[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

[ https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852706#comment-15852706 ] ASF subversion and git services commented on LOG4J2-1431: - Commit

Jenkins build is still unstable: Log4j 2.x #2646

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org