[jira] [Comment Edited] (LOG4J2-2870) Dependency on PropertyChangeListener and PropertyChangeEvent

[ https://issues.apache.org/jira/browse/LOG4J2-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17696435#comment-17696435 ] Jannik Zuther edited comment on LOG4J2-2870 at 3/4/23 2:30 PM: --- Still

[jira] [Commented] (LOG4J2-2870) Dependency on PropertyChangeListener and PropertyChangeEvent

[ https://issues.apache.org/jira/browse/LOG4J2-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17696435#comment-17696435 ] Jannik Zuther commented on LOG4J2-2870: --- Still seems to be the case in `3.0.0` as of right now. I

[jira] [Updated] (LOG4J2-3652) jlink creates broken runtime image when using "--strip-debug" flag

[ https://issues.apache.org/jira/browse/LOG4J2-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jannik Zuther updated LOG4J2-3652: -- Description: I'm trying out the current `3.0.0-SNAPSHOT` (not sure if they have a unique ID

[jira] [Updated] (LOG4J2-3652) jlink creates broken runtime image when using "--strip-debug" flag

[ https://issues.apache.org/jira/browse/LOG4J2-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jannik Zuther updated LOG4J2-3652: -- Description: I'm trying out the current `3.0.0-SNAPSHOT` (not sure if they have a unique ID

[jira] [Updated] (LOG4J2-3652) jlink creates broken runtime image when using "--strip-debug" flag

[ https://issues.apache.org/jira/browse/LOG4J2-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jannik Zuther updated LOG4J2-3652: -- Description: I'm trying out the current `3.0.0-SNAPSHOT` (that's the ones from 2023-03-03

[jira] [Updated] (LOG4J2-3652) jlink creates broken runtime image when using "--strip-debug" flag

[ https://issues.apache.org/jira/browse/LOG4J2-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jannik Zuther updated LOG4J2-3652: -- Description: I'm trying out the current `3.0.0-SNAPSHOT` (that's the ones from 2023-03-03

[jira] [Created] (LOG4J2-3652) jlink creates broken runtime image when using "--strip-debug" flag

Jannik Zuther created LOG4J2-3652: - Summary: jlink creates broken runtime image when using "--strip-debug" flag Key: LOG4J2-3652 URL: https://issues.apache.org/jira/browse/LOG4J2-3652 Proj

[jira] [Created] (LOG4J2-3651) 2.20.0 release notes change pattern confused ("for")

Philippe Cloutier created LOG4J2-3651: - Summary: 2.20.0 release notes change pattern confused ("for") Key: LOG4J2-3651 URL: https://issues.apache.org/jira/browse/LOG4J2-3651 Projec

[jira] [Commented] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17695304#comment-17695304 ] Piotr Karwasz commented on LOG4J2-3650: --- For future reference I'll add a link to the [discussion

[jira] [Work logged] (LOG4J2-2332) Unresolved variables in any file appender

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

[jira] [Work logged] (LOG4J2-3040) ShutdownCallbackRegistry should be part of log4j-api, not log4j-core

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

[jira] [Work logged] (LOG4J2-3040) ShutdownCallbackRegistry should be part of log4j-api, not log4j-core

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

[jira] [Work logged] (LOG4J2-2332) Unresolved variables in any file appender

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

[jira] [Work logged] (LOG4J2-2399) Reusable Messages do not respect log4j.format.msg.async

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

[jira] [Work logged] (LOG4J2-2902) LoaderUtil#getClassLoaders throws a SecurityException trying to access system class loader

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

[jira] [Work logged] (LOG4J2-3068) JCToolsBlockingQueueFactory can use MpscBlockingConsumerArrayQueue

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

[jira] [Work logged] (LOG4J2-3319) Add minimal support for log4j 1.2 API bundle usage in Eclipse IDE

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

[jira] [Work logged] (LOG4J2-3332) SmtpAppender: add capability to send buffered messages as an email attachment (text, zip, gzip)

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

[jira] [Work logged] (LOG4J2-3040) ShutdownCallbackRegistry should be part of log4j-api, not log4j-core

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

[jira] [Work logged] (LOG4J2-3558) Make the default thread priority configurable

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

[jira] [Work logged] (LOG4J2-3627) PatternLayout: %xEx{ [ "short" | depth]} not working

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

[jira] [Work logged] (LOG4J2-2947) LogBuilder should not have no-op default methods

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

[jira] [Work logged] (LOG4J2-3280) Support for microsecond precision in RFC5424Layout

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

[jira] [Work logged] (LOG4J2-3280) Support for microsecond precision in RFC5424Layout

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

[jira] [Work logged] (LOG4J2-3627) PatternLayout: %xEx{ [ "short" | depth]} not working

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

[jira] [Work logged] (LOG4J2-2947) LogBuilder should not have no-op default methods

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

[jira] [Work logged] (LOG4J2-3280) Support for microsecond precision in RFC5424Layout

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

[jira] [Work logged] (LOG4J2-3040) ShutdownCallbackRegistry should be part of log4j-api, not log4j-core

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

[jira] [Work logged] (LOG4J2-3319) Add minimal support for log4j 1.2 API bundle usage in Eclipse IDE

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

[jira] [Work logged] (LOG4J2-3068) JCToolsBlockingQueueFactory can use MpscBlockingConsumerArrayQueue

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

[jira] [Work logged] (LOG4J2-3332) SmtpAppender: add capability to send buffered messages as an email attachment (text, zip, gzip)

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

[jira] [Work logged] (LOG4J2-3558) Make the default thread priority configurable

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

[jira] [Work logged] (LOG4J2-3122) Logging to Log4j2 MongoDb4 Appender get ERROR on trace, debug and info level.

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

[jira] [Work logged] (LOG4J2-2902) LoaderUtil#getClassLoaders throws a SecurityException trying to access system class loader

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

[jira] [Work logged] (LOG4J2-2954) Shutdown callbacks registered in LoggerContext.setUpShutdownHook() aren't strongly referenced

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

[jira] [Work logged] (LOG4J2-2399) Reusable Messages do not respect log4j.format.msg.async

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

[jira] [Work logged] (LOG4J2-2656) Add possibility to ignore exception if kafka connection error occurred

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

[jira] [Work logged] (LOG4J2-2332) Unresolved variables in any file appender

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

[jira] [Work logged] (LOG4J2-2750) Setting to disable extended stack trace for layouts

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

[jira] [Closed] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-3650. --- Closing this due to info provider by the reporter. > Release 2.20.0 missing artifa

[jira] [Comment Edited] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17693694#comment-17693694 ] Jon Wilmoth edited comment on LOG4J2-3650 at 2/26/23 8:26 PM: -- Thank you

[jira] [Commented] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17693694#comment-17693694 ] Jon Wilmoth commented on LOG4J2-3650: - Thank you [~rgoers].  We use the ListAppender in our narrow

[jira] [Resolved] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-3650. - Resolution: Information Provided > Release 2.20.0 missing artifa

[jira] [Comment Edited] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17692254#comment-17692254 ] Ralph Goers edited comment on LOG4J2-3650 at 2/22/23 3:57 PM

[jira] [Commented] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17692254#comment-17692254 ] Ralph Goers commented on LOG4J2-3650: - This is going to be a bit of a long answer.   The work

[jira] [Comment Edited] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17692049#comment-17692049 ] Piotr Karwasz edited comment on LOG4J2-3650 at 2/22/23 9:26 AM

[jira] [Commented] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17692049#comment-17692049 ] Piotr Karwasz commented on LOG4J2-3650: --- [~jonwilm...@yahoo.com], Log4j2 Core has *no* {{tests

[jira] [Commented] (LOG4J2-3650) Release 2.20.0 missing artifacts

[ https://issues.apache.org/jira/browse/LOG4J2-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17691999#comment-17691999 ] Volkan Yazici commented on LOG4J2-3650: --- Test JARs are not supposed to be consumed by users. Would

[jira] [Created] (LOG4J2-3650) Release 2.20.0 missing artifacts

Jon Wilmoth created LOG4J2-3650: --- Summary: Release 2.20.0 missing artifacts Key: LOG4J2-3650 URL: https://issues.apache.org/jira/browse/LOG4J2-3650 Project: Log4j 2 Issue Type: Bug

[jira] [Commented] (LOG4J2-1990) ConcurrentModificationException logging a parameter of type Map

[ https://issues.apache.org/jira/browse/LOG4J2-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17686726#comment-17686726 ] Gus Heck commented on LOG4J2-1990: -- Hmm this makes debugging custom appenders that rely

[jira] [Updated] (LOG4J2-3642) Consider Osgi versions older than 1.5 as not available.

[ https://issues.apache.org/jira/browse/LOG4J2-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3642: -- Priority: Minor (was: Major) > Consider Osgi versions older than 1.5 as not availa

[jira] [Updated] (LOG4J2-3642) Consider Osgi versions older than 1.5 as not available.

[ https://issues.apache.org/jira/browse/LOG4J2-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3642: -- Fix Version/s: 2.20.0 > Consider Osgi versions older than 1.5 as not availa

[jira] [Resolved] (LOG4J2-3642) Consider Osgi versions older than 1.5 as not available.

[ https://issues.apache.org/jira/browse/LOG4J2-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz resolved LOG4J2-3642. --- Resolution: Fixed > Consider Osgi versions older than 1.5 as not availa

[jira] [Commented] (LOG4J2-3649) catching() is missing in KotlinLogger

[ https://issues.apache.org/jira/browse/LOG4J2-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17686078#comment-17686078 ] Matt Sicker commented on LOG4J2-3649: - Oh nice catch before I got around to a 1.3.0 release. You can

[jira] [Updated] (LOG4J2-3649) catching() is missing in KotlinLogger

[ https://issues.apache.org/jira/browse/LOG4J2-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-3649: Fix Version/s: Kotlin 1.3.0 > catching() is missing in KotlinLog

[jira] [Commented] (LOG4J2-3624) NoClassDefFoundError initializing PropertiesUtil in Servlet 2.5 container

[ https://issues.apache.org/jira/browse/LOG4J2-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17685494#comment-17685494 ] Piotr Karwasz commented on LOG4J2-3624: --- [~nsush...@openfinance.com], I still can't reproduce

[jira] [Updated] (LOG4J2-3621) Log4J 2.19 breaks contract of order of loading of System Properties

[ https://issues.apache.org/jira/browse/LOG4J2-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3621: -- Priority: Minor (was: Major) > Log4J 2.19 breaks contract of order of loading of Sys

[jira] [Resolved] (LOG4J2-3621) Log4J 2.19 breaks contract of order of loading of System Properties

[ https://issues.apache.org/jira/browse/LOG4J2-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz resolved LOG4J2-3621. --- Resolution: Fixed > Log4J 2.19 breaks contract of order of loading of System Propert

[jira] [Updated] (LOG4J2-3621) Log4J 2.19 breaks contract of order of loading of System Properties

[ https://issues.apache.org/jira/browse/LOG4J2-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3621: -- Fix Version/s: 2.20.0 > Log4J 2.19 breaks contract of order of loading of System Propert

[jira] [Created] (LOG4J2-3649) catching() is missing in KotlinLogger

Björn Michael created LOG4J2-3649: - Summary: catching() is missing in KotlinLogger Key: LOG4J2-3649 URL: https://issues.apache.org/jira/browse/LOG4J2-3649 Project: Log4j 2 Issue Type: Bug

[jira] [Commented] (LOG4J2-3621) Log4J 2.19 breaks contract of order of loading of System Properties

[ https://issues.apache.org/jira/browse/LOG4J2-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17685193#comment-17685193 ] Adwait Kumar Singh commented on LOG4J2-3621: [~pkarwasz], I went via another approach

[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3601: -- Fix Version/s: 2.20.0 > log4j-slf4j2: change of dependency scope for log4j-c

[jira] [Resolved] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz resolved LOG4J2-3601. --- Resolution: Fixed > log4j-slf4j2: change of dependency scope for log4j-c

[jira] [Commented] (LOG4J2-3621) Log4J 2.19 breaks contract of order of loading of System Properties

[ https://issues.apache.org/jira/browse/LOG4J2-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17684343#comment-17684343 ] Piotr Karwasz commented on LOG4J2-3621: --- [~adwsingh], The loop in {{Environment#get}} uses

[jira] [Comment Edited] (LOG4J2-3621) Log4J 2.19 breaks contract of order of loading of System Properties

[ https://issues.apache.org/jira/browse/LOG4J2-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17684303#comment-17684303 ] Adwait Kumar Singh edited comment on LOG4J2-3621 at 2/5/23 1:39 PM

[jira] [Commented] (LOG4J2-3621) Log4J 2.19 breaks contract of order of loading of System Properties

[ https://issues.apache.org/jira/browse/LOG4J2-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17684303#comment-17684303 ] Adwait Kumar Singh commented on LOG4J2-3621: [~pkarwasz] Can I use a simpler approach

[jira] [Resolved] (LOG4J2-3615) Fix Log4j API OSGI encapsulation problem

[ https://issues.apache.org/jira/browse/LOG4J2-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz resolved LOG4J2-3615. --- Resolution: Fixed > Fix Log4j API OSGI encapsulation prob

[jira] [Updated] (LOG4J2-3647) Equivalence of `LogBuilder` and `Logger` calls

[ https://issues.apache.org/jira/browse/LOG4J2-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3647: -- Fix Version/s: 2.20.0 > Equivalence of `LogBuilder` and `Logger` ca

[jira] [Updated] (LOG4J2-3615) Fix Log4j API OSGI encapsulation problem

[ https://issues.apache.org/jira/browse/LOG4J2-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3615: -- Fix Version/s: 2.20.0 > Fix Log4j API OSGI encapsulation prob

[jira] [Resolved] (LOG4J2-3647) Equivalence of `LogBuilder` and `Logger` calls

[ https://issues.apache.org/jira/browse/LOG4J2-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz resolved LOG4J2-3647. --- Resolution: Fixed > Equivalence of `LogBuilder` and `Logger` ca

[jira] [Resolved] (LOG4J2-3648) No appender references provided to AsyncAppender: appenderRefs

[ https://issues.apache.org/jira/browse/LOG4J2-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz resolved LOG4J2-3648. --- Resolution: Duplicate Closing this, since it duplicates [Github Issues #1227|https

[jira] [Updated] (LOG4J2-3648) No appender references provided to AsyncAppender: appenderRefs

[ https://issues.apache.org/jira/browse/LOG4J2-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3648: -- Issue Type: Question (was: Bug) > No appender references provided to AsyncAppen

[jira] [Updated] (LOG4J2-3648) No appender references provided to AsyncAppender: appenderRefs

[ https://issues.apache.org/jira/browse/LOG4J2-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3648: -- Priority: Minor (was: Major) > No appender references provided to AsyncAppen

[jira] [Created] (LOG4J2-3648) No appender references provided to AsyncAppender: appenderRefs

Viraj Jasani created LOG4J2-3648: Summary: No appender references provided to AsyncAppender: appenderRefs Key: LOG4J2-3648 URL: https://issues.apache.org/jira/browse/LOG4J2-3648 Project: Log4j 2

[jira] [Closed] (LOG4J2-3643) RollingFile, Cron and SizeBased Triggers: Wrong time in names of archives

[ https://issues.apache.org/jira/browse/LOG4J2-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Rosinskii closed LOG4J2-3643. -- it's working as expected. thank you! [^log4j2_afterFix.log] > RollingFile, Cron and SizeBa

[jira] [Updated] (LOG4J2-3643) RollingFile, Cron and SizeBased Triggers: Wrong time in names of archives

[ https://issues.apache.org/jira/browse/LOG4J2-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Rosinskii updated LOG4J2-3643: --- Attachment: log4j2_afterFix.log > RollingFile, Cron and SizeBased Triggers: Wrong t

[jira] [Comment Edited] (LOG4J2-3643) RollingFile, Cron and SizeBased Triggers: Wrong time in names of archives

[ https://issues.apache.org/jira/browse/LOG4J2-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17679882#comment-17679882 ] Ralph Goers edited comment on LOG4J2-3643 at 1/23/23 4:35 PM: -- Fixed

[jira] [Resolved] (LOG4J2-3643) RollingFile, Cron and SizeBased Triggers: Wrong time in names of archives

[ https://issues.apache.org/jira/browse/LOG4J2-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-3643. - Fix Version/s: 2.20.0 Resolution: Fixed Fixed in release-2. and master. > RollingF

[jira] [Comment Edited] (LOG4J2-3643) RollingFile, Cron and SizeBased Triggers: Wrong time in names of archives

[ https://issues.apache.org/jira/browse/LOG4J2-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17679792#comment-17679792 ] Ivan Rosinskii edited comment on LOG4J2-3643 at 1/23/23 1:43 PM: - thank

[jira] [Commented] (LOG4J2-3643) RollingFile, Cron and SizeBased Triggers: Wrong time in names of archives

[ https://issues.apache.org/jira/browse/LOG4J2-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17679792#comment-17679792 ] Ivan Rosinskii commented on LOG4J2-3643: thank you! we would be really glad

[jira] [Commented] (LOG4J2-3643) RollingFile, Cron and SizeBased Triggers: Wrong time in names of archives

[ https://issues.apache.org/jira/browse/LOG4J2-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17679624#comment-17679624 ] Ralph Goers commented on LOG4J2-3643: - I've looked at the log and looked at the code and it isn't

[jira] [Resolved] (LOG4J2-3628) Migrate from maven-changes-plugin to a merge-conflict-free Markdown-based solution

[ https://issues.apache.org/jira/browse/LOG4J2-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici resolved LOG4J2-3628. --- Resolution: Fixed > Migrate from maven-changes-plugin to a merge-conflict-free Markd

[jira] [Closed] (LOG4J2-3628) Migrate from maven-changes-plugin to a merge-conflict-free Markdown-based solution

[ https://issues.apache.org/jira/browse/LOG4J2-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici closed LOG4J2-3628. - Assignee: Volkan Yazici > Migrate from maven-changes-plugin to a merge-conflict-free Markd

[jira] [Commented] (LOG4J2-3647) Equivalence of `LogBuilder` and `Logger` calls

[ https://issues.apache.org/jira/browse/LOG4J2-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17677416#comment-17677416 ] Ralph Goers commented on LOG4J2-3647: - Yes, I see the problem now. > Equivalence of `LogBuil

[jira] [Commented] (LOG4J2-1794) Programmatic reconfiguration doesn't affect existing loggers

[ https://issues.apache.org/jira/browse/LOG4J2-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17677167#comment-17677167 ] Ralph Goers commented on LOG4J2-1794: - Configurator.initialize() will essentially be a noop

[jira] [Updated] (LOG4J2-1794) Programmatic reconfiguration doesn't affect existing loggers

[ https://issues.apache.org/jira/browse/LOG4J2-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1794: Issue Type: Documentation (was: Bug) > Programmatic reconfiguration doesn't affect exist

[jira] [Resolved] (LOG4J2-3228) Nothing should implement Serializable in Log4j 3

[ https://issues.apache.org/jira/browse/LOG4J2-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-3228. - Resolution: Fixed Merged in master. > Nothing should implement Serializable in Log4

[jira] [Assigned] (LOG4J2-3228) Nothing should implement Serializable in Log4j 3

[ https://issues.apache.org/jira/browse/LOG4J2-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker reassigned LOG4J2-3228: --- Assignee: Matt Sicker > Nothing should implement Serializable in Log4

[jira] [Commented] (LOG4J2-3647) Equivalence of `LogBuilder` and `Logger` calls

[ https://issues.apache.org/jira/browse/LOG4J2-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17676949#comment-17676949 ] Piotr Karwasz commented on LOG4J2-3647: --- [~rgoers], Yes, {{isEnabled}} is called in both cases

[jira] [Commented] (LOG4J2-3647) Equivalence of `LogBuilder` and `Logger` calls

[ https://issues.apache.org/jira/browse/LOG4J2-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17676948#comment-17676948 ] Ralph Goers commented on LOG4J2-3647: - This makes no sense to me. AbstractLogger does {code:java

[jira] [Created] (LOG4J2-3647) Equivalence of `LogBuilder` and `Logger` calls

Piotr Karwasz created LOG4J2-3647: - Summary: Equivalence of `LogBuilder` and `Logger` calls Key: LOG4J2-3647 URL: https://issues.apache.org/jira/browse/LOG4J2-3647 Project: Log4j 2 Issue

[jira] [Updated] (LOG4J2-3598) Upgrade to SLF4J 2.0.1

[ https://issues.apache.org/jira/browse/LOG4J2-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3598: -- Fix Version/s: 2.20.0 > Upgrade to SLF4J 2.

[jira] [Updated] (LOG4J2-3638) Provide a Maven plugin to inline location information

[ https://issues.apache.org/jira/browse/LOG4J2-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3638: -- Component/s: Transform > Provide a Maven plugin to inline location informat

[jira] [Resolved] (LOG4J2-3638) Provide a Maven plugin to inline location information

[ https://issues.apache.org/jira/browse/LOG4J2-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz resolved LOG4J2-3638. --- Resolution: Fixed > Provide a Maven plugin to inline location informat

[jira] [Updated] (LOG4J2-3638) Provide a Maven plugin to inline location information

[ https://issues.apache.org/jira/browse/LOG4J2-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3638: -- Fix Version/s: transform-0.1.0 > Provide a Maven plugin to inline location informat

[jira] [Updated] (LOG4J2-3643) RollingFile, Cron and SizeBased Triggers: Wrong time in names of archives

[ https://issues.apache.org/jira/browse/LOG4J2-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Rosinskii updated LOG4J2-3643: --- Attachment: log4j.log > RollingFile, Cron and SizeBased Triggers: Wrong time in na

[jira] [Commented] (LOG4J2-3643) RollingFile, Cron and SizeBased Triggers: Wrong time in names of archives

[ https://issues.apache.org/jira/browse/LOG4J2-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17656057#comment-17656057 ] Ivan Rosinskii commented on LOG4J2-3643: Configuration: {code:java

[jira] [Commented] (LOG4J2-3624) NoClassDefFoundError initializing PropertiesUtil in Servlet 2.5 container

[ https://issues.apache.org/jira/browse/LOG4J2-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17654685#comment-17654685 ] Nicholas Sushkin commented on LOG4J2-3624: -- Hi, Piotr, Thanks for taking a look at it. I tried

[jira] [Updated] (LOG4J2-3624) NoClassDefFoundError initializing PropertiesUtil in Servlet 2.5 container

[ https://issues.apache.org/jira/browse/LOG4J2-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas Sushkin updated LOG4J2-3624: - Attachment: image-2023-01-04-18-53-27-006.png > NoClassDefFoundError initializ

[jira] [Commented] (LOG4J2-3646) Log4jBridgeHandler does not work OTB on Tomcat 10.1

[ https://issues.apache.org/jira/browse/LOG4J2-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17654398#comment-17654398 ] Matthew Firth commented on LOG4J2-3646: --- [~pkarwasz] - creating a custom LogManager that mimics

<    1   2   3   4   5   6   7   8   9   10   >