[jira] [Assigned] (LOG4J2-3193) ConfigurationFactory cannot find config file property normalized by EnvironmentPropertySource

2022-03-09 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz reassigned LOG4J2-3193: - Assignee: Piotr Karwasz > ConfigurationFactory cannot find config file property normali

[jira] [Comment Edited] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

2022-03-09 Thread Radim Tlusty (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504035#comment-17504035 ] Radim Tlusty edited comment on LOG4J2-3423 at 3/10/22, 6:53 AM: --

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

2022-03-09 Thread Radim Tlusty (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504035#comment-17504035 ] Radim Tlusty commented on LOG4J2-3423: -- [~pkarwasz] - I've successfully tested you

[jira] [Assigned] (LOG4J2-3366) Fix order of property sources

2022-03-09 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz reassigned LOG4J2-3366: - Assignee: Piotr Karwasz > Fix order of property sources > -

[GitHub] [logging-log4j2] garydgregory commented on pull request #788: Update documentation

2022-03-09 Thread GitBox
garydgregory commented on pull request #788: URL: https://github.com/apache/logging-log4j2/pull/788#issuecomment-1063505013 The "with" style is old, the "set" style is new. We already deprecated a bunch of "with" methods in favor of "set" methods. -- This is an automated message from the

[GitHub] [logging-log4j2] garydgregory commented on a change in pull request #788: Update documentation

2022-03-09 Thread GitBox
garydgregory commented on a change in pull request #788: URL: https://github.com/apache/logging-log4j2/pull/788#discussion_r823216495 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/config/LoggerConfig.java ## @@ -214,7 +214,7 @@ public Filter getFilter()

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

2022-03-09 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503900#comment-17503900 ] Piotr Karwasz commented on LOG4J2-3423: --- [~rtlusty], I generated a snapshot with t

[jira] [Comment Edited] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

2022-03-09 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503900#comment-17503900 ] Piotr Karwasz edited comment on LOG4J2-3423 at 3/9/22, 10:58 PM: -

[jira] [Comment Edited] (LOG4J2-2975) SLF4J fluent API fails to capture call site location due to missing LoggingEventAware implementation

2022-03-09 Thread Ceki Gulcu (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503880#comment-17503880 ] Ceki Gulcu edited comment on LOG4J2-2975 at 3/9/22, 10:44 PM:

[jira] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

2022-03-09 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3423 ] Piotr Karwasz deleted comment on LOG4J2-3423: --- was (Author: pkarwasz): [~rtlusty], can you check the latest snapshot, if it solves your problem? There are multiple paths that use {{URLConn

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

2022-03-09 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503888#comment-17503888 ] Piotr Karwasz commented on LOG4J2-3423: --- [~rtlusty], can you check the latest snap

[jira] [Commented] (LOG4J2-2975) SLF4J fluent API fails to capture call site location due to missing LoggingEventAware implementation

2022-03-09 Thread Ceki Gulcu (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503880#comment-17503880 ] Ceki Gulcu commented on LOG4J2-2975: SLF4J version 1.8 has been superseded by versio

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

2022-03-09 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503879#comment-17503879 ] ASF subversion and git services commented on LOG4J2-3423: - Commi

[GitHub] [logging-log4j2] ppkarwasz merged pull request #784: [LOG4J2-3423] Refactoring of URLConnection code

2022-03-09 Thread GitBox
ppkarwasz merged pull request #784: URL: https://github.com/apache/logging-log4j2/pull/784 -- 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: notific

[jira] [Resolved] (LOG4J2-3418) Proper registration of Log4j2CloudConfigLoggingSystem

2022-03-09 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz resolved LOG4J2-3418. --- Fix Version/s: 2.17.3 Resolution: Fixed > Proper registration of Log4j2CloudConfigLog

[jira] [Commented] (LOG4J2-3418) Proper registration of Log4j2CloudConfigLoggingSystem

2022-03-09 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503856#comment-17503856 ] Piotr Karwasz commented on LOG4J2-3418: --- [~membersound], I merged my PR and genera

[jira] [Assigned] (LOG4J2-3418) Proper registration of Log4j2CloudConfigLoggingSystem

2022-03-09 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz reassigned LOG4J2-3418: - Assignee: Piotr Karwasz > Proper registration of Log4j2CloudConfigLoggingSystem > -

[jira] [Commented] (LOG4J2-3418) Proper registration of Log4j2CloudConfigLoggingSystem

2022-03-09 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503841#comment-17503841 ] ASF subversion and git services commented on LOG4J2-3418: - Commi

[GitHub] [logging-log4j2] ppkarwasz merged pull request #777: [LOG4J2-3418] Fix Log4j2CloudConfigLoggingSystem registration

2022-03-09 Thread GitBox
ppkarwasz merged pull request #777: URL: https://github.com/apache/logging-log4j2/pull/777 -- 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: notific

[GitHub] [logging-log4j2] phreed commented on a change in pull request #788: Update documentation

2022-03-09 Thread GitBox
phreed commented on a change in pull request #788: URL: https://github.com/apache/logging-log4j2/pull/788#discussion_r823038591 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/config/LoggerConfig.java ## @@ -214,7 +214,7 @@ public Filter getFilter() {

[GitHub] [logging-log4j2] phreed commented on a change in pull request #788: Update documentation

2022-03-09 Thread GitBox
phreed commented on a change in pull request #788: URL: https://github.com/apache/logging-log4j2/pull/788#discussion_r823038591 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/config/LoggerConfig.java ## @@ -214,7 +214,7 @@ public Filter getFilter() {

[GitHub] [logging-log4j2] ppkarwasz commented on a change in pull request #788: Update documentation

2022-03-09 Thread GitBox
ppkarwasz commented on a change in pull request #788: URL: https://github.com/apache/logging-log4j2/pull/788#discussion_r823034883 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/config/LoggerConfig.java ## @@ -884,7 +893,7 @@ public Filter getFilter() {

[GitHub] [logging-log4j2] phreed commented on a change in pull request #788: Update documentation

2022-03-09 Thread GitBox
phreed commented on a change in pull request #788: URL: https://github.com/apache/logging-log4j2/pull/788#discussion_r823025534 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/config/LoggerConfig.java ## @@ -214,7 +214,7 @@ public Filter getFilter() {

[jira] [Commented] (LOG4J2-3427) ServiceLoader usage in a servlet environment

2022-03-09 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503797#comment-17503797 ] ASF subversion and git services commented on LOG4J2-3427: - Commi

[jira] [Commented] (LOG4J2-3427) ServiceLoader usage in a servlet environment

2022-03-09 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503794#comment-17503794 ] ASF subversion and git services commented on LOG4J2-3427: - Commi

[GitHub] [logging-log4j2] ppkarwasz merged pull request #787: [LOG4J2-3427] Add a ServiceLoader tool

2022-03-09 Thread GitBox
ppkarwasz merged pull request #787: URL: https://github.com/apache/logging-log4j2/pull/787 -- 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: notific

[GitHub] [logging-log4j2] ppkarwasz commented on a change in pull request #788: Update documentation

2022-03-09 Thread GitBox
ppkarwasz commented on a change in pull request #788: URL: https://github.com/apache/logging-log4j2/pull/788#discussion_r822975410 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/config/LoggerConfig.java ## @@ -214,7 +214,7 @@ public Filter getFilter() {

[GitHub] [logging-log4j2] ppkarwasz commented on pull request #777: [LOG4J2-3418] Fix Log4j2CloudConfigLoggingSystem registration

2022-03-09 Thread GitBox
ppkarwasz commented on pull request #777: URL: https://github.com/apache/logging-log4j2/pull/777#issuecomment-1063246235 > Could you add documentation how to activate this feature in future? The behavior of the artifact does not change: you add it to the classpath and Spring Boot det

[GitHub] [logging-log4j2] garydgregory commented on a change in pull request #789: [LOG4J2-3419] Adds support for custom Log4j 1.x levels

2022-03-09 Thread GitBox
garydgregory commented on a change in pull request #789: URL: https://github.com/apache/logging-log4j2/pull/789#discussion_r822971298 ## File path: log4j-1.2-api/src/main/java/org/apache/log4j/Priority.java ## @@ -96,6 +96,7 @@ transient int level; transient String le

[GitHub] [logging-log4j2] ppkarwasz opened a new pull request #789: [LOG4J2-3419] Adds support for custom Log4j 1.x levels

2022-03-09 Thread GitBox
ppkarwasz opened a new pull request #789: URL: https://github.com/apache/logging-log4j2/pull/789 Adds support for custom Log4j 1.x levels in the form `level_name#class_name`. Levels defined directly in Log4j 2.x can be used in the bridge using the form `level_name#org.apache.logging.

[jira] [Commented] (LOG4J2-3345) log4j-jpl must handle parameters as MessageFormat args

2022-03-09 Thread Carter Kozak (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503605#comment-17503605 ] Carter Kozak commented on LOG4J2-3345: -- The System.Logger API that this implements

[jira] [Commented] (LOG4J2-3345) log4j-jpl must handle parameters as MessageFormat args

2022-03-09 Thread Markus Spann (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503589#comment-17503589 ] Markus Spann commented on LOG4J2-3345: -- [~ckozak], this is a breaking change for ap

[jira] [Resolved] (LOG4J2-3431) log4j bridge API :- Log message filtering based on UtilLoggingLevel fails and all messages are written into log files

2022-03-09 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz resolved LOG4J2-3431. --- Resolution: Duplicate > log4j bridge API :- Log message filtering based on UtilLoggingLevel

[jira] [Commented] (LOG4J2-3431) log4j bridge API :- Log message filtering based on UtilLoggingLevel fails and all messages are written into log files

2022-03-09 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503470#comment-17503470 ] Piotr Karwasz commented on LOG4J2-3431: --- Custom levelsĀ  (even those in {{UtilLoggi

[jira] [Assigned] (LOG4J2-3431) log4j bridge API :- Log message filtering based on UtilLoggingLevel fails and all messages are written into log files

2022-03-09 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz reassigned LOG4J2-3431: - Assignee: Piotr Karwasz > log4j bridge API :- Log message filtering based on UtilLoggin

[jira] [Created] (LOG4J2-3432) RollingFileAppender fails after 100 backup cycles if filePattern contains "%04i" .

2022-03-09 Thread Carl Smotricz (Jira)
Carl Smotricz created LOG4J2-3432: - Summary: RollingFileAppender fails after 100 backup cycles if filePattern contains "%04i" . Key: LOG4J2-3432 URL: https://issues.apache.org/jira/browse/LOG4J2-3432

[jira] [Updated] (LOG4J2-3431) log4j bridge API :- Log message filtering based on UtilLoggingLevel fails and all messages are written into log files

2022-03-09 Thread Tukesh (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tukesh updated LOG4J2-3431: --- Description: log4j bridge API :- Log message filtering based on UtilLoggingLevel fails and all messages are

[jira] [Created] (LOG4J2-3431) log4j bridge API :- Log message filtering based on UtilLoggingLevel fails and all messages are written into log files

2022-03-09 Thread Tukesh (Jira)
Tukesh created LOG4J2-3431: -- Summary: log4j bridge API :- Log message filtering based on UtilLoggingLevel fails and all messages are written into log files Key: LOG4J2-3431 URL: https://issues.apache.org/jira/browse/LOG4