[jira] (LOG4J2-3532) Log4j 2.x is not compatible with Jansi 2.x

[ https://issues.apache.org/jira/browse/LOG4J2-3532 ] Ralph Goers deleted comment on LOG4J2-3532: - was (Author: ralph.go...@dslextreme.com): [~pkarwasz]I believe this comment is on the wrong Jira issue. > Log4j 2.x is not compatible with Jansi

[jira] [Commented] (LOG4J2-3531) log4j2.xml cannot be parsed on WebSphere

[ https://issues.apache.org/jira/browse/LOG4J2-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552525#comment-17552525 ] Piotr Karwasz commented on LOG4J2-3531: --- [~simonikula], personally I find the properties

[jira] (LOG4J2-3532) Log4j 2.x is not compatible with Jansi 2.x

[ https://issues.apache.org/jira/browse/LOG4J2-3532 ] Piotr Karwasz deleted comment on LOG4J2-3532: --- was (Author: pkarwasz): [~simonikula], personally I find the properties configuration much less readable than the XML config (actually any

[GitHub] [logging-log4j2] yueki1993 commented on a diff in pull request #924: [LOG4J2-3534] Fix LevelRangeFilterBuilder to align with log4j1's behavior

yueki1993 commented on code in PR #924: URL: https://github.com/apache/logging-log4j2/pull/924#discussion_r894062873 ## log4j-1.2-api/src/test/java/org/apache/log4j/config/PropertiesConfigurationTest.java: ## @@ -129,6 +129,28 @@ public void

[GitHub] [logging-log4j2] yueki1993 commented on a diff in pull request #924: [LOG4J2-3534] Fix LevelRangeFilterBuilder to align with log4j1's behavior

yueki1993 commented on code in PR #924: URL: https://github.com/apache/logging-log4j2/pull/924#discussion_r894062873 ## log4j-1.2-api/src/test/java/org/apache/log4j/config/PropertiesConfigurationTest.java: ## @@ -129,6 +129,28 @@ public void

[jira] [Commented] (LOG4J2-3532) Log4j 2.x is not compatible with Jansi 2.x

[ https://issues.apache.org/jira/browse/LOG4J2-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552453#comment-17552453 ] Ralph Goers commented on LOG4J2-3532: - [~pkarwasz]I believe this comment is on the wrong Jira issue.

[jira] [Closed] (LOG4J2-2941) zero-padding configuration problem

[ https://issues.apache.org/jira/browse/LOG4J2-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-2941. --- > zero-padding configuration problem > -- > > Key:

[jira] [Commented] (LOG4J2-3532) Log4j 2.x is not compatible with Jansi 2.x

[ https://issues.apache.org/jira/browse/LOG4J2-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552337#comment-17552337 ] Piotr Karwasz commented on LOG4J2-3532: --- [~simonikula], personally I find the properties

[jira] [Commented] (LOG4J2-3531) log4j2.xml cannot be parsed on WebSphere

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

[jira] [Updated] (LOG4J2-3531) log4j2.xml cannot be parsed on WebSphere

[ https://issues.apache.org/jira/browse/LOG4J2-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3531: -- Fix Version/s: 2.18.0 > log4j2.xml cannot be parsed on WebSphere >

[jira] [Resolved] (LOG4J2-3531) log4j2.xml cannot be parsed on WebSphere

[ https://issues.apache.org/jira/browse/LOG4J2-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz resolved LOG4J2-3531. --- Resolution: Fixed > log4j2.xml cannot be parsed on WebSphere >

[jira] [Commented] (LOG4J2-3531) log4j2.xml cannot be parsed on WebSphere

[ https://issues.apache.org/jira/browse/LOG4J2-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552263#comment-17552263 ] Simo Nikula commented on LOG4J2-3531: - [~pkarwasz] 20220609.132510 solved situation. Thanks for

[GitHub] [logging-log4j2] yueki1993 commented on a diff in pull request #924: [LOG4J2-3534] Fix LevelRangeFilterBuilder to align with log4j1's behavior

yueki1993 commented on code in PR #924: URL: https://github.com/apache/logging-log4j2/pull/924#discussion_r893542193 ## log4j-1.2-api/src/test/java/org/apache/log4j/config/PropertiesConfigurationTest.java: ## @@ -326,4 +326,9 @@ public void testEnhancedRollingFileAppender()

[jira] [Updated] (LOG4J2-3534) LevelRangeFilterBuilder loses compatibility with log4j1.

[ https://issues.apache.org/jira/browse/LOG4J2-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yohei Ueki updated LOG4J2-3534: --- Description:

[jira] [Updated] (LOG4J2-3534) LevelRangeFilterBuilder loses compatibility with log4j1.

[ https://issues.apache.org/jira/browse/LOG4J2-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yohei Ueki updated LOG4J2-3534: --- Description:

[GitHub] [logging-log4j2] yueki1993 opened a new pull request, #924: [LOG4J2-3534] Fix LevelRangeFilterBuilder to align with log4j1's behavior

yueki1993 opened a new pull request, #924: URL: https://github.com/apache/logging-log4j2/pull/924 https://issues.apache.org/jira/browse/LOG4J2-3534 -- 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-3533) Desired Log4j 2.17.x files not available

[ https://issues.apache.org/jira/browse/LOG4J2-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552205#comment-17552205 ] Gary D. Gregory commented on LOG4J2-3533: - Log4j 2 files are here:

[jira] [Created] (LOG4J2-3534) LevelRangeFilterBuilder loses compatibility with log4j1.

Yohei Ueki created LOG4J2-3534: -- Summary: LevelRangeFilterBuilder loses compatibility with log4j1. Key: LOG4J2-3534 URL: https://issues.apache.org/jira/browse/LOG4J2-3534 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-3531) log4j2.xml cannot be parsed on WebSphere

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

[jira] [Resolved] (LOG4J2-2941) zero-padding configuration problem

[ https://issues.apache.org/jira/browse/LOG4J2-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jasonyu resolved LOG4J2-2941. - Fix Version/s: 2.18.0 (was: 2.16.0) Resolution: Resolved > zero-padding

[jira] [Commented] (LOG4J2-2941) zero-padding configuration problem

[ https://issues.apache.org/jira/browse/LOG4J2-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552182#comment-17552182 ] jasonyu commented on LOG4J2-2941: - It has been corrected in release-2.x branch. This issue should be

[GitHub] [logging-log4j2] dependabot[bot] opened a new pull request, #923: Bump actions/setup-python from 3.1.2 to 4

dependabot[bot] opened a new pull request, #923: URL: https://github.com/apache/logging-log4j2/pull/923 Bumps [actions/setup-python](https://github.com/actions/setup-python) from 3.1.2 to 4. Release notes Sourced from

[jira] [Comment Edited] (LOG4J2-3531) log4j2.xml cannot be parsed on WebSphere

[ https://issues.apache.org/jira/browse/LOG4J2-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552047#comment-17552047 ] Simo Nikula edited comment on LOG4J2-3531 at 6/9/22 8:48 AM: - Latest

[jira] [Commented] (LOG4J2-3531) log4j2.xml cannot be parsed on WebSphere

[ https://issues.apache.org/jira/browse/LOG4J2-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552047#comment-17552047 ] Simo Nikula commented on LOG4J2-3531: - Latest snapshot was this and it failed in similar way

[jira] [Created] (LOG4J2-3533) Desired Log4j 2.17.x files not available

Harshit created LOG4J2-3533: --- Summary: Desired Log4j 2.17.x files not available Key: LOG4J2-3533 URL: https://issues.apache.org/jira/browse/LOG4J2-3533 Project: Log4j 2 Issue Type: Bug Affects

[jira] [Commented] (LOG4J2-3531) log4j2.xml cannot be parsed on WebSphere

[ https://issues.apache.org/jira/browse/LOG4J2-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552011#comment-17552011 ] Piotr Karwasz commented on LOG4J2-3531: --- [~simonikula], all Apache snapshots are under the

[jira] [Commented] (LOG4J2-3531) log4j2.xml cannot be parsed on WebSphere

[ https://issues.apache.org/jira/browse/LOG4J2-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17551991#comment-17551991 ] Simo Nikula commented on LOG4J2-3531: - [~pkarwasz] I solved problem by converting configuration to