[
https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177466#comment-16177466
]
Remko Popma commented on LOG4J2-2052:
-
Actually I just realized this can be as simple
Github user jasontedor commented on the issue:
https://github.com/apache/logging-log4j2/pull/109
I can confirm that as well, both the unit tests we have that rely on this
are passing now, and the application is logging the correct location when `%l`
is used as a pattern.
---
Github user rgoers commented on the issue:
https://github.com/apache/logging-log4j2/pull/109
I just tried running one of my webapps on tomcat under Java 9. Although I
didn't have much success due to Spring (that is a different story) I do see the
location information correctly.
---
[
https://issues.apache.org/jira/browse/LOG4J2-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frank Steudle updated LOG4J2-2053:
--
Description:
Today I updated my fitnesse project to use the 2.9.0 versions of log4-core and
lo
Frank Steudle created LOG4J2-2053:
-
Summary: Exception java.nio.charset.UnsupportedCharsetException:
cp65001 in 2.9.0
Key: LOG4J2-2053
URL: https://issues.apache.org/jira/browse/LOG4J2-2053
Project: L
[
https://issues.apache.org/jira/browse/LOG4J2-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176087#comment-16176087
]
Remko Popma commented on LOG4J2-2035:
-
>From Log4j 2.9, async loggers now require LMA
[
https://issues.apache.org/jira/browse/LOG4J2-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176076#comment-16176076
]
Corneliu C commented on LOG4J2-2035:
Hi, any reasons for not using latest version 3.3
