[GitHub] [logging-log4j2] UditE5 commented on a change in pull request #608: Restrict LDAP access via JNDI

UditE5 commented on a change in pull request #608: URL: https://github.com/apache/logging-log4j2/pull/608#discussion_r774917352 ## File path: log4j-core/src/test/java/org/apache/logging/log4j/core/lookup/JndiLdapLookupTest.java ## @@ -0,0 +1,124 @@ +/* + * Licensed to the

[jira] [Commented] (LOG4J2-3279) Alternative mitigation documented for CVE-2021-45105 doesn't work for messages without context lookup if the Log4J2 consumers are not on version >= 2.15

[ https://issues.apache.org/jira/browse/LOG4J2-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464909#comment-17464909 ] sumeet sharma commented on LOG4J2-3279: --- Hi [~rgoers] - thanks for the explanation. I think I

[jira] [Reopened] (LOG4J2-3279) Alternative mitigation documented for CVE-2021-45105 doesn't work for messages without context lookup if the Log4J2 consumers are not on version >= 2.15

[ https://issues.apache.org/jira/browse/LOG4J2-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sumeet sharma reopened LOG4J2-3279: --- > Alternative mitigation documented for CVE-2021-45105 doesn't work for > messages without

[jira] [Created] (LOGCXX-546) Multi threaded applications run at single threaded speed

Dr Stephen L S Webb created LOGCXX-546: -- Summary: Multi threaded applications run at single threaded speed Key: LOGCXX-546 URL: https://issues.apache.org/jira/browse/LOGCXX-546 Project: Log4cxx

[jira] [Comment Edited] (LOGCXX-532) Static objects and deleting

[ https://issues.apache.org/jira/browse/LOGCXX-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464869#comment-17464869 ] Dr Stephen L S Webb edited comment on LOGCXX-532 at 12/24/21, 3:07 AM:

[jira] [Assigned] (LOG4J2-3282) log4j-to-jul JDK Logging Bridge

[ https://issues.apache.org/jira/browse/LOG4J2-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-3282: --- Assignee: Michael Vorburger > log4j-to-jul JDK Logging Bridge >

[jira] [Commented] (LOG4J2-3282) log4j-to-jul JDK Logging Bridge

[ https://issues.apache.org/jira/browse/LOG4J2-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464874#comment-17464874 ] Ralph Goers commented on LOG4J2-3282: - The guidance is basically that the artifactId and package

[jira] [Commented] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464872#comment-17464872 ] Ralph Goers commented on LOG4J2-3278: - Wow. I wasn't aware that ever worked with JsonTemplateLayout.

[jira] [Comment Edited] (LOGCXX-532) Static objects and deleting

[ https://issues.apache.org/jira/browse/LOGCXX-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464869#comment-17464869 ] Dr Stephen L S Webb edited comment on LOGCXX-532 at 12/24/21, 2:31 AM:

[jira] [Comment Edited] (LOGCXX-532) Static objects and deleting

[ https://issues.apache.org/jira/browse/LOGCXX-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464869#comment-17464869 ] Dr Stephen L S Webb edited comment on LOGCXX-532 at 12/24/21, 2:25 AM:

[jira] [Commented] (LOGCXX-532) Static objects and deleting

[ https://issues.apache.org/jira/browse/LOGCXX-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464869#comment-17464869 ] Dr Stephen L S Webb commented on LOGCXX-532: I suggest LoggerRepository (or Hierarchy) hold a

[jira] [Commented] (LOG4J2-3282) log4j-to-jul JDK Logging Bridge

[ https://issues.apache.org/jira/browse/LOG4J2-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464870#comment-17464870 ] Michael Vorburger commented on LOG4J2-3282: --- Do committers have any guidance what Java package

[jira] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278 ] Richard Gomez deleted comment on LOG4J2-3278: --- was (Author: JIRAUSER282146): I believe this is because 2.17.0 limited lookups to the Java protocol.

[jira] [Updated] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhangZhichun updated LOG4J2-3278: - Attachment: log-spring-1.xml > SpringLookup log4j2 2.17.0 version Invalidation >

[jira] [Commented] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464863#comment-17464863 ] ZhangZhichun commented on LOG4J2-3278: -- This is my all configuration. [^log-spring.xml]

[jira] [Updated] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhangZhichun updated LOG4J2-3278: - Attachment: JHJsonEventLayoutV1.json > SpringLookup log4j2 2.17.0 version Invalidation >

[jira] [Updated] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhangZhichun updated LOG4J2-3278: - Attachment: log-spring.xml > SpringLookup log4j2 2.17.0 version Invalidation >

[jira] [Updated] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhangZhichun updated LOG4J2-3278: - Attachment: (was: JHJsonEventLayoutV1-1.json) > SpringLookup log4j2 2.17.0 version

[jira] [Updated] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhangZhichun updated LOG4J2-3278: - Attachment: (was: JHJsonEventLayoutV1.json) > SpringLookup log4j2 2.17.0 version

[jira] [Updated] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhangZhichun updated LOG4J2-3278: - Attachment: (was: log-spring-1.xml) > SpringLookup log4j2 2.17.0 version Invalidation >

[jira] [Updated] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhangZhichun updated LOG4J2-3278: - Attachment: (was: log-spring.xml) > SpringLookup log4j2 2.17.0 version Invalidation >

[jira] [Updated] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhangZhichun updated LOG4J2-3278: - Attachment: JHJsonEventLayoutV1-1.json > SpringLookup log4j2 2.17.0 version Invalidation >

[jira] [Updated] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhangZhichun updated LOG4J2-3278: - Attachment: log-spring.xml > SpringLookup log4j2 2.17.0 version Invalidation >

[jira] [Updated] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhangZhichun updated LOG4J2-3278: - Attachment: JHJsonEventLayoutV1.json > SpringLookup log4j2 2.17.0 version Invalidation >

[jira] [Commented] (LOG4J2-3282) log4j-to-jul JDK Logging Bridge

[ https://issues.apache.org/jira/browse/LOG4J2-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464855#comment-17464855 ] Michael Vorburger commented on LOG4J2-3282: ---

[GitHub] [logging-log4j2] vorburger opened a new pull request #653: (DRAFT, WIP - DO NOT MERGE YET, BUT INITIAL REVIEW WELCOME) Release 2.x log4j-to-jul JDK Logging Bridge (LOG4J2-3282)

vorburger opened a new pull request #653: URL: https://github.com/apache/logging-log4j2/pull/653 https://issues.apache.org/jira/browse/LOG4J2-3282 -- 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

[jira] [Commented] (LOG4J2-3285) JIRA tickets should be able to be assigned to Contributors and not just Committers

[ https://issues.apache.org/jira/browse/LOG4J2-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464852#comment-17464852 ] Remko Popma commented on LOG4J2-3285: - !image-2021-12-24-09-45-20-341.png! The above are the

[jira] [Comment Edited] (LOG4J2-3285) JIRA tickets should be able to be assigned to Contributors and not just Committers

[ https://issues.apache.org/jira/browse/LOG4J2-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464852#comment-17464852 ] Remko Popma edited comment on LOG4J2-3285 at 12/24/21, 12:47 AM: -

[jira] [Updated] (LOG4J2-3285) JIRA tickets should be able to be assigned to Contributors and not just Committers

[ https://issues.apache.org/jira/browse/LOG4J2-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-3285: Attachment: image-2021-12-24-09-45-20-341.png > JIRA tickets should be able to be assigned to

[GitHub] [logging-log4cxx] swebb2066 commented on pull request #87: Imported and slightly cleaned up throughput tests

swebb2066 commented on pull request #87: URL: https://github.com/apache/logging-log4cxx/pull/87#issuecomment-1000584520 > Part of the performance testing is to also help us find areas where we can better parallelize the logging. There are probably a number of places we can replace a mutex

[jira] [Resolved] (LOG4J2-3285) JIRA tickets should be able to be assigned to Contributors and not just Committers

[ https://issues.apache.org/jira/browse/LOG4J2-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-3285. - Resolution: Fixed Jira issues can be assigned to contributors. However, your user wasn't

[jira] [Updated] (LOG4J2-3282) log4j-to-jul JDK Logging Bridge

[ https://issues.apache.org/jira/browse/LOG4J2-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated LOG4J2-3282: -- Summary: log4j-to-jul JDK Logging Bridge (was: log4j-to-jul Adapter) > log4j-to-jul

[jira] [Commented] (LOG4J2-3279) Alternative mitigation documented for CVE-2021-45105 doesn't work for messages without context lookup if the Log4J2 consumers are not on version >= 2.15

[ https://issues.apache.org/jira/browse/LOG4J2-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464841#comment-17464841 ] Ralph Goers commented on LOG4J2-3279: - The mitigations listed for each CVE are ONLY for that CVE.

[jira] [Resolved] (LOG4J2-3279) Alternative mitigation documented for CVE-2021-45105 doesn't work for messages without context lookup if the Log4J2 consumers are not on version >= 2.15

[ https://issues.apache.org/jira/browse/LOG4J2-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-3279. - Resolution: Information Provided > Alternative mitigation documented for CVE-2021-45105 doesn't

[jira] [Commented] (LOG4J2-2819) Add support for specifying an SSL configuration for SmtpAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464812#comment-17464812 ] Remko Popma commented on LOG4J2-2819: - The fix for this issue has been backported into 2.12.3 for

[jira] [Created] (LOG4J2-3287) document log4j2.system.properties file

Volkan Yazici created LOG4J2-3287: - Summary: document log4j2.system.properties file Key: LOG4J2-3287 URL: https://issues.apache.org/jira/browse/LOG4J2-3287 Project: Log4j 2 Issue Type:

[jira] [Updated] (LOG4J2-3184) Support Scala 3

[ https://issues.apache.org/jira/browse/LOG4J2-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-3184: Affects Version/s: Scala 12.0 (was: 2.14.1) > Support Scala 3 >

[jira] [Resolved] (LOG4J2-3184) Support Scala 3

[ https://issues.apache.org/jira/browse/LOG4J2-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-3184. - Assignee: Matt Sicker Resolution: Fixed Merged in master. Will be part of upcoming 13.0

[jira] [Updated] (LOG4J2-3184) Support Scala 3

[ https://issues.apache.org/jira/browse/LOG4J2-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-3184: Fix Version/s: Scala 13.0 > Support Scala 3 > --- > > Key:

[GitHub] [logging-log4j-scala] jvz commented on pull request #5: scala 3 support

jvz commented on pull request #5: URL: https://github.com/apache/logging-log4j-scala/pull/5#issuecomment-1000515452 Thanks so much for the PR! I'll work on a release candidate sometime today (assuming the rest of the build still works as documented). -- This is an automated message

[GitHub] [logging-log4j-scala] jvz merged pull request #5: scala 3 support

jvz merged pull request #5: URL: https://github.com/apache/logging-log4j-scala/pull/5 -- 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:

[GitHub] [logging-log4j-scala] pjfanning commented on pull request #5: scala 3 support

pjfanning commented on pull request #5: URL: https://github.com/apache/logging-log4j-scala/pull/5#issuecomment-1000514813 @jvz I'm happy to get this merged as is -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[jira] [Commented] (LOG4J2-3282) log4j-to-jul Adapter

[ https://issues.apache.org/jira/browse/LOG4J2-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464789#comment-17464789 ] Gary D. Gregory commented on LOG4J2-3282: - Hello [~vorburger] Feel free to provide a PR on

[jira] [Closed] (LOG4J2-3286) 2.17 has reverted LOG4J-2972 fix in AppenderControl but change not in history

[ https://issues.apache.org/jira/browse/LOG4J2-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3286. Resolution: Information Provided Closing as information provided. If there's a bug, please don't

[jira] [Updated] (LOG4J2-3286) 2.17 has reverted LOG4J-2972 fix in AppenderControl but change not in history

[ https://issues.apache.org/jira/browse/LOG4J2-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-3286: - Issue Type: Question (was: Bug) > 2.17 has reverted LOG4J-2972 fix in AppenderControl but

[jira] [Commented] (LOG4J2-3272) Enable Git and GitHub for log4j 1.2 repository

[ https://issues.apache.org/jira/browse/LOG4J2-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464783#comment-17464783 ] Matt Sicker commented on LOG4J2-3272: - Speaking of naming pedantry, if you're hoping to modularize

[jira] (LOG4J2-3272) Enable Git and GitHub for log4j 1.2 repository

[ https://issues.apache.org/jira/browse/LOG4J2-3272 ] Matt Sicker deleted comment on LOG4J2-3272: - was (Author: jvz): I'd be ok with an actual rename of the old repo into the new one to keep the existing stars/PRs/forks/etc. on GitHub. For

[jira] [Commented] (LOG4J2-3272) Enable Git and GitHub for log4j 1.2 repository

[ https://issues.apache.org/jira/browse/LOG4J2-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464779#comment-17464779 ] Matt Sicker commented on LOG4J2-3272: - I'd be ok with an actual rename of the old repo into the new

[jira] [Commented] (LOG4J2-3272) Enable Git and GitHub for log4j 1.2 repository

[ https://issues.apache.org/jira/browse/LOG4J2-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464774#comment-17464774 ] Vladimir Sitnikov commented on LOG4J2-3272: --- [~rgoers], [~vy], [~rpopma], As Chris Lambertus

[jira] [Commented] (LOG4J2-3272) Enable Git and GitHub for log4j 1.2 repository

[ https://issues.apache.org/jira/browse/LOG4J2-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464767#comment-17464767 ] Vladimir Sitnikov commented on LOG4J2-3272: --- I have raised INFRA question regarding

[jira] [Commented] (LOG4J2-3286) 2.17 has reverted LOG4J-2972 fix in AppenderControl but change not in history

[ https://issues.apache.org/jira/browse/LOG4J2-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464765#comment-17464765 ] Carter Kozak commented on LOG4J2-3286: -- The AsyncAppender fix (and tests which verify it) are still

[jira] [Created] (LOG4J2-3286) 2.17 has reverted LOG4J-2972 fix in AppenderControl but change not in history

Ben Thurley created LOG4J2-3286: --- Summary: 2.17 has reverted LOG4J-2972 fix in AppenderControl but change not in history Key: LOG4J2-3286 URL: https://issues.apache.org/jira/browse/LOG4J2-3286 Project:

[jira] [Commented] (LOG4J2-3284) log4j-to-slf4j does not take the MessageFactory into account

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

[jira] [Closed] (LOG4J2-3284) log4j-to-slf4j does not take the MessageFactory into account

[ https://issues.apache.org/jira/browse/LOG4J2-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3284. Thanks for the contribution! > log4j-to-slf4j does not take the MessageFactory into account >

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

[ https://issues.apache.org/jira/browse/LOG4J2-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464744#comment-17464744 ] Gary D. Gregory commented on LOG4J2-3122: - I can reproduce this with 2.14.1 but NOT with 2.17.0.

[jira] [Resolved] (LOG4J2-3284) log4j-to-slf4j does not take the MessageFactory into account

[ https://issues.apache.org/jira/browse/LOG4J2-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-3284. -- Resolution: Fixed > log4j-to-slf4j does not take the MessageFactory into account >

[GitHub] [logging-log4j2] carterkozak merged pull request #651: Fix MessageFactory support bug in SLF4JLoggerContext

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

[jira] [Commented] (LOG4J2-3264) MapLookup should lookup MapMessage before properties

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

[jira] [Resolved] (LOG4J2-3264) MapLookup should lookup MapMessage before properties

[ https://issues.apache.org/jira/browse/LOG4J2-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-3264. -- Fix Version/s: 2.17.1 Resolution: Fixed Please verify and close > MapLookup should

[jira] [Commented] (LOG4J2-3264) MapLookup should lookup MapMessage before properties

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

[GitHub] [logging-log4j2] carterkozak merged pull request #646: LOG4J2-3264: Fix MapLookup to lookup MapMessage before DefaultMap

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

[GitHub] [logging-log4j2] garydgregory commented on pull request #646: LOG4J2-3264: Fix MapLookup to lookup MapMessage before DefaultMap

garydgregory commented on pull request #646: URL: https://github.com/apache/logging-log4j2/pull/646#issuecomment-1000445117 > @garydgregory You have an active disapproval on this PR, is there anything you're waiting for? Approved, thank you for the reminder. -- This is an

[GitHub] [logging-log4j2] carterkozak commented on pull request #646: LOG4J2-3264: Fix MapLookup to lookup MapMessage before DefaultMap

carterkozak commented on pull request #646: URL: https://github.com/apache/logging-log4j2/pull/646#issuecomment-1000444053 @garydgregory You have an active disapproval on this PR, is there anything you're waiting for? -- This is an automated message from the Apache Git Service. To

[jira] [Updated] (LOG4J2-3285) JIRA tickets should be able to be assigned to Contributors and not just Committers

[ https://issues.apache.org/jira/browse/LOG4J2-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated LOG4J2-3285: -- Description: New issue to follow up re. this from LOG4J2-3284, this is not about code

[jira] [Commented] (LOG4J2-3284) log4j-to-slf4j does not take the MessageFactory into account

[ https://issues.apache.org/jira/browse/LOG4J2-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464720#comment-17464720 ] Michael Vorburger commented on LOG4J2-3284: --- Oh! Really? Let's follow-up on that through a

[jira] [Created] (LOG4J2-3285) JIRA tickets should be able to be assigned to Contributors and not just Committers

Michael Vorburger created LOG4J2-3285: - Summary: JIRA tickets should be able to be assigned to Contributors and not just Committers Key: LOG4J2-3285 URL: https://issues.apache.org/jira/browse/LOG4J2-3285

[GitHub] [logging-log4j2] carterkozak merged pull request #652: release 2.x clean slf4j javadoc

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

[jira] [Commented] (LOG4J2-3284) log4j-to-slf4j does not take the MessageFactory into account

[ https://issues.apache.org/jira/browse/LOG4J2-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464714#comment-17464714 ] Carter Kozak commented on LOG4J2-3284: -- I don't believe this Jira configuration allows us to assign

[jira] [Commented] (LOG4J2-3284) log4j-to-slf4j does not take the MessageFactory into account

[ https://issues.apache.org/jira/browse/LOG4J2-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464712#comment-17464712 ] Michael Vorburger commented on LOG4J2-3284: --- [~ckozak] would you be willing to assign this bug

[jira] [Updated] (LOG4J2-3282) log4j-to-jul Adapter

[ https://issues.apache.org/jira/browse/LOG4J2-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated LOG4J2-3282: -- Summary: log4j-to-jul Adapter (was: log4j-to-jul Bridge) > log4j-to-jul Adapter >

[GitHub] [logging-log4j2] carterkozak commented on pull request #651: Fix MessageFactory support bug in SLF4JLoggerContext

carterkozak commented on pull request #651: URL: https://github.com/apache/logging-log4j2/pull/651#issuecomment-1000429985 lgtm, thanks for the contribution! I'll get this merged once tests complete. I've filed https://issues.apache.org/jira/browse/LOG4J2-3284 for tracking. --

[jira] [Created] (LOG4J2-3284) log4j-to-slf4j does not take the MessageFactory into account

Carter Kozak created LOG4J2-3284: Summary: log4j-to-slf4j does not take the MessageFactory into account Key: LOG4J2-3284 URL: https://issues.apache.org/jira/browse/LOG4J2-3284 Project: Log4j 2

[jira] [Assigned] (LOG4J2-3284) log4j-to-slf4j does not take the MessageFactory into account

[ https://issues.apache.org/jira/browse/LOG4J2-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-3284: Assignee: Carter Kozak > log4j-to-slf4j does not take the MessageFactory into account >

[jira] [Commented] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464709#comment-17464709 ] Carter Kozak commented on LOG4J2-3278: -- In 2.17.0 we limited recursive evaluation of lookups at

[GitHub] [logging-log4j2] vorburger commented on pull request #651: Fix MessageFactory support bug in SLF4JLoggerContext

vorburger commented on pull request #651: URL: https://github.com/apache/logging-log4j2/pull/651#issuecomment-1000425549 BTW just FYI this PR is a result of my staring at this code in the context of [LOG4J2-3282](https://issues.apache.org/jira/browse/LOG4J2-3282) - it seemed like a Good

[jira] [Commented] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464703#comment-17464703 ] Richard Gomez commented on LOG4J2-3278: --- I believe this is because 2.17.0 limited lookups to the

[GitHub] [logging-log4j2] vorburger commented on pull request #651: Fix MessageFactory support bug in SLF4JLoggerContext

vorburger commented on pull request #651: URL: https://github.com/apache/logging-log4j2/pull/651#issuecomment-1000424173 > Please base your PR on the branch release-2.x. done > It would be helpful to describe what has been resolved rather than using the description `fixed bug

[jira] [Commented] (LOG4J2-3283) Add error-prone to build

[ https://issues.apache.org/jira/browse/LOG4J2-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464702#comment-17464702 ] Carter Kozak commented on LOG4J2-3283: -- Yes, several years ago I added it to the master branch, but

[jira] [Updated] (LOG4J2-3283) Add error-prone to build

[ https://issues.apache.org/jira/browse/LOG4J2-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated LOG4J2-3283: -- Description: Would this project, the Log4j community, welcome a contribution to add

[jira] [Created] (LOG4J2-3283) Add error-prone to build

Michael Vorburger created LOG4J2-3283: - Summary: Add error-prone to build Key: LOG4J2-3283 URL: https://issues.apache.org/jira/browse/LOG4J2-3283 Project: Log4j 2 Issue Type: Improvement

[GitHub] [logging-log4j2] larrywest42 edited a comment on pull request #642: Add Link to Release History

larrywest42 edited a comment on pull request #642: URL: https://github.com/apache/logging-log4j2/pull/642#issuecomment-1000418438 That's a helpful change, especially as the most recent version mentioned in "RELEASE-NOTES.md" is `2.11.0`, from 2018. -- This is an automated message from

[GitHub] [logging-log4j2] larrywest42 commented on pull request #642: Add Link to Release History

larrywest42 commented on pull request #642: URL: https://github.com/apache/logging-log4j2/pull/642#issuecomment-1000418438 That's a helpful change, especially as the most recent version mentioned in "RELEASE-NOTE.md" is `2.11.0`, from 2018. -- This is an automated message from the

[GitHub] [logging-log4j2] carterkozak commented on pull request #651: Fix obvious bug in SLF4JLoggerContext (and related typo in LoggerTest)

carterkozak commented on pull request #651: URL: https://github.com/apache/logging-log4j2/pull/651#issuecomment-1000417982 It would be helpful to describe what has been resolved rather than using the description `fixed bug in ClassName` ;-) I'd appreciate it if you could PR into

[GitHub] [logging-log4j2] garydgregory commented on pull request #651: Fix obvious bug in SLF4JLoggerContext (and related typo in LoggerTest)

garydgregory commented on pull request #651: URL: https://github.com/apache/logging-log4j2/pull/651#issuecomment-1000416627 Hello @vorburger, Please base your PR on the branch release-2.x. -- This is an automated message from the Apache Git Service. To respond to the message,

[GitHub] [logging-log4j2] vorburger commented on pull request #651: Fix obvious bug in SLF4JLoggerContext (and related typo in LoggerTest)

vorburger commented on pull request #651: URL: https://github.com/apache/logging-log4j2/pull/651#issuecomment-1000414777 Builds failing? I've opened https://issues.apache.org/jira/browse/LOG4J2-3229. BTW should I be raising a 2nd PR to cherry-pick this to `release-2.x` from

[jira] [Commented] (LOG4J2-56) Level.toLevel throws IllegalArgumentException instead of returning default Level

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

[jira] [Commented] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464686#comment-17464686 ] Michael Vorburger commented on LOG4J2-1180: ---

[jira] [Commented] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464685#comment-17464685 ] Michael Vorburger commented on LOG4J2-1180: --- {quote}[~garydgregory], 

[GitHub] [logging-log4j2] vorburger opened a new pull request #652: release 2.x clean slf4j javadoc

vorburger opened a new pull request #652: URL: https://github.com/apache/logging-log4j2/pull/652 - LOG4J2-2236 Removed unnecessary dependency on jcommander since Log4j uses embedded picocli since 2.9. - [LOG4J2-2243] Cannot see or copy all of certain JAnsi exception messages on Windows

[jira] [Commented] (LOG4J2-3281) PropertiesConfiguration.buildAppender not adding filters to appender

[ https://issues.apache.org/jira/browse/LOG4J2-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464684#comment-17464684 ] Gary D. Gregory commented on LOG4J2-3281: - >Did yours produce a different outcome? Yes, please

[GitHub] [logging-log4j2] vorburger opened a new pull request #651: Fix obvious bug in SLF4JLoggerContext (and related typo in LoggerTest)

vorburger opened a new pull request #651: URL: https://github.com/apache/logging-log4j2/pull/651 Yo Log4j maintainers - hope this helps? -- 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

[jira] [Commented] (LOG4J2-3281) PropertiesConfiguration.buildAppender not adding filters to appender

[ https://issues.apache.org/jira/browse/LOG4J2-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464680#comment-17464680 ] Fábio Constantino commented on LOG4J2-3281: --- {{Log4j is being called through a 

[GitHub] [logging-log4j2] vy commented on pull request #648: Revert "remove cache-action"

vy commented on pull request #648: URL: https://github.com/apache/logging-log4j2/pull/648#issuecomment-1000398388 Spam. -- 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

[jira] [Commented] (LOG4J2-3274) Log4j2 deadlock version 2.16

[ https://issues.apache.org/jira/browse/LOG4J2-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464662#comment-17464662 ] Faisal Khan commented on LOG4J2-3274: - Thank you [~rgoers]. Closing this issue. > Log4j2 deadlock

[jira] [Closed] (LOG4J2-3274) Log4j2 deadlock version 2.16

[ https://issues.apache.org/jira/browse/LOG4J2-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Faisal Khan closed LOG4J2-3274. --- > Log4j2 deadlock version 2.16 > > > Key: LOG4J2-3274 >

[jira] [Commented] (LOG4J2-3282) log4j-to-jul Bridge

[ https://issues.apache.org/jira/browse/LOG4J2-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464661#comment-17464661 ] Michael Vorburger commented on LOG4J2-3282: --- I understand that this would also be possible (as

[jira] [Created] (LOG4J2-3282) log4j-to-jul Bridge

Michael Vorburger created LOG4J2-3282: - Summary: log4j-to-jul Bridge Key: LOG4J2-3282 URL: https://issues.apache.org/jira/browse/LOG4J2-3282 Project: Log4j 2 Issue Type: Improvement

[jira] [Comment Edited] (LOG4J2-3281) PropertiesConfiguration.buildAppender not adding filters to appender

[ https://issues.apache.org/jira/browse/LOG4J2-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464652#comment-17464652 ] Gary D. Gregory edited comment on LOG4J2-3281 at 12/23/21, 3:38 PM:

[jira] [Commented] (LOG4J2-3281) PropertiesConfiguration.buildAppender not adding filters to appender

[ https://issues.apache.org/jira/browse/LOG4J2-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464652#comment-17464652 ] Gary D. Gregory commented on LOG4J2-3281: - [~coredumped]  So far, things look OK based on the

[jira] [Commented] (LOG4J2-3281) PropertiesConfiguration.buildAppender not adding filters to appender

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

  1   2   >