rgoers commented on PR #820:
URL: https://github.com/apache/logging-log4j2/pull/820#issuecomment-1098529039
Please add a README to this that essentially says that SLF4J 2.0 is in alpha
status, so is not considered to be production ready. Accordingly, users may
experience breakages with
[
https://issues.apache.org/jira/browse/LOG4J2-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17521951#comment-17521951
]
Matt Sicker commented on LOG4J2-3476:
-
Back when that class was initially written, I don't think
[
https://issues.apache.org/jira/browse/LOG4J2-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Lin resolved LOG4J2-3475.
Fix Version/s: 2.17.3
Resolution: Fixed
Fixed in
[
https://issues.apache.org/jira/browse/LOG4J2-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Lin updated LOG4J2-3475:
---
Description:
ppkarwasz opened a new pull request, #820:
URL: https://github.com/apache/logging-log4j2/pull/820
Support for SFL4J stack valued MDC entries is emulated by adding JSON-ish
arrays as values in `ThreadContext`.
I don't expect performance to be an issue in this feature.
--
This is an
[
https://issues.apache.org/jira/browse/LOGCXX-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Jipa closed LOGCXX-552.
--
Resolution: Not A Problem
Hi,
The fact you said is not anymore needed to copy log4cxx.hw and
[
https://issues.apache.org/jira/browse/LOG4J2-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17521726#comment-17521726
]
ASF subversion and git services commented on LOG4J2-3475:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17521727#comment-17521727
]
ASF subversion and git services commented on LOG4J2-3475:
-
Commit
ppkarwasz merged PR #818:
URL: https://github.com/apache/logging-log4j2/pull/818
--
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.
To unsubscribe, e-mail:
filipc opened a new pull request, #819:
URL: https://github.com/apache/logging-log4j2/pull/819
There is a typo in definition of context stack resolver. Should be **mdc**
what stands for Mapped Diagnostic Context, was **ndc** by mistake.
--
This is an automated message from the Apache Git
[
https://issues.apache.org/jira/browse/LOG4J2-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-3476:
Description:
The current implementation of ApiLogger::setLevel is to throw an
Remko Popma created LOG4J2-3476:
---
Summary: Support JUL ApiLogger::setLevel
Key: LOG4J2-3476
URL: https://issues.apache.org/jira/browse/LOG4J2-3476
Project: Log4j 2
Issue Type: New Feature
vy commented on PR #818:
URL: https://github.com/apache/logging-log4j2/pull/818#issuecomment-1097735689
Note that `changes.xml` needs to updated too.
--
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
vy merged PR #20:
URL: https://github.com/apache/logging-log4j-scala/pull/20
--
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.
To unsubscribe, e-mail:
jjlin commented on PR #818:
URL: https://github.com/apache/logging-log4j2/pull/818#issuecomment-1097678696
@ppkarwasz unit test added
--
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
ppkarwasz commented on PR #818:
URL: https://github.com/apache/logging-log4j2/pull/818#issuecomment-1097621181
@jjlin: this looks good to me. Can you add a unity test that fails on the
currently released code?
--
This is an automated message from the Apache Git Service.
To respond to the
16 matches
Mail list logo
