[jira] [Commented] (LOGCXX-533) cannot use log4cxx header files with clang++

[ https://issues.apache.org/jira/browse/LOGCXX-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408447#comment-17408447 ] Robert Middleton commented on LOGCXX-533: - 0.12.0 was released 2021-05-01.   I

[jira] [Closed] (LOGCXX-533) cannot use log4cxx header files with clang++

[ https://issues.apache.org/jira/browse/LOGCXX-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Middleton closed LOGCXX-533. --- Resolution: Resolved > cannot use log4cxx header files with clang++ > ---

[jira] [Comment Edited] (LOGCXX-533) cannot use log4cxx header files with clang++

[ https://issues.apache.org/jira/browse/LOGCXX-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408347#comment-17408347 ] Sergei Delov edited comment on LOGCXX-533 at 9/1/21, 7:43 PM: -

[jira] [Commented] (LOGCXX-533) cannot use log4cxx header files with clang++

[ https://issues.apache.org/jira/browse/LOGCXX-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408347#comment-17408347 ] Sergei Delov commented on LOGCXX-533: - Robert, We do not use log4cxx distribution di

[CI][UNSTABLE] Logging/log4j/release-2.x#341 has test failures

BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/341/ Project: release-2.x Date of build: Wed, 01 Sep 2021 13:28:14 + Build duration: 1 hr 3 min and counting JUnit Tests Name: (root) Failed: 0 test(s), P

[GitHub] [logging-log4j2] vy commented on pull request #576: JTL InstantFormatter invalidates cached FixedDateFormat as expected

vy commented on pull request #576: URL: https://github.com/apache/logging-log4j2/pull/576#issuecomment-910287283 Cherry-picked to `master`. -- 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 sp

[GitHub] [logging-log4j2] vy merged pull request #576: JTL InstantFormatter invalidates cached FixedDateFormat as expected

vy merged pull request #576: URL: https://github.com/apache/logging-log4j2/pull/576 -- 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: notifications-

[GitHub] [logging-log4j2] vy commented on pull request #576: JTL InstantFormatter invalidates cached FixedDateFormat as expected

vy commented on pull request #576: URL: https://github.com/apache/logging-log4j2/pull/576#issuecomment-910285774 Great catch! Thanks so much @carterkozak! -- 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

[GitHub] [logging-log4j2] carterkozak opened a new pull request #576: JTL InstantFormatter invalidates cached FixedDateFormat as expected

carterkozak opened a new pull request #576: URL: https://github.com/apache/logging-log4j2/pull/576 Previously more precise patterns would be cached unexpectedly within a millisecond interval, all using the microsecond or nanosecond value of the first event that millisecond. -- This

[jira] [Commented] (LOG4J2-3154) Support NameAbbreviator in ExceptionResolver when using JsonTemplateLayout

[ https://issues.apache.org/jira/browse/LOG4J2-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408093#comment-17408093 ] Volkan Yazici commented on LOG4J2-3154: --- Thanks for sharing a solution [~BigMichi1

[jira] [Created] (LOG4J2-3156) Stacktraces with xEx conversion are expanded resulting in duplicate/redundant line in the trace

Ali Akcan created LOG4J2-3156: - Summary: Stacktraces with xEx conversion are expanded resulting in duplicate/redundant line in the trace Key: LOG4J2-3156 URL: https://issues.apache.org/jira/browse/LOG4J2-3156