Re: [PR] Bump org.eclipse.persistence:org.eclipse.persistence.jpa from 2.7.11 to 2.7.13 (logging-log4j2)

2023-11-01 Thread via GitHub
Franetse7 commented on PR #1933: URL: https://github.com/apache/logging-log4j2/pull/1933#issuecomment-1789845352 Ok thanks for congratulation Le mar. 31 oct. 2023 à 19:01, dependabot[bot] ***@***.***> a écrit : > OK, I won't notify you again about this release, but will g

Re: [I] How do I check the version of log4j library version deployed in the Java runtime? (logging-log4j2)

2023-11-01 Thread via GitHub
pantdeepak commented on issue #1923: URL: https://github.com/apache/logging-log4j2/issues/1923#issuecomment-1789596089 Thank you very much for your prompt attention to this issue. Much appreciated. -- This is an automated message from the Apache Git Service. To respond to the message, pl

Re: [I] notEmpty still outputs text when variable is empty (logging-log4j2)

2023-11-01 Thread via GitHub
simontankersley commented on issue #1922: URL: https://github.com/apache/logging-log4j2/issues/1922#issuecomment-1789246904 > Would you mind giving 2.22.0-SNAPSHOT a try once [the associated CI run](https://github.com/apache/logging-log4j2/actions/runs/6717848523) successfully finishes, pl

Re: [PR] Bump com.github.luben:zstd-jni from 1.5.5-8 to 1.5.5-9 (logging-log4j2)

2023-11-01 Thread via GitHub
github-actions[bot] commented on PR #1938: URL: https://github.com/apache/logging-log4j2/pull/1938#issuecomment-1788758813 Changes are applied by CI in 282d533a39850cc4758d1e78e2ac66898d1d4769 -- This is an automated message from the Apache Git Service. To respond to the message, please lo

Re: [PR] Bump com.github.luben:zstd-jni from 1.5.5-8 to 1.5.5-9 (logging-log4j2)

2023-11-01 Thread via GitHub
github-actions[bot] closed pull request #1938: Bump com.github.luben:zstd-jni from 1.5.5-8 to 1.5.5-9 URL: https://github.com/apache/logging-log4j2/pull/1938 -- 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 t

[jira] [Work logged] (LOG4J2-3672) Avoid invoking DateFormatSymbols.getZoneStrings() in FastDateParser

2023-11-01 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3672?focusedWorklogId=888252&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-888252 ] ASF GitHub Bot logged work on LOG4J2-3672: -- Author: ASF GitHub Bot

Re: [PR] LOG4J2-3672 Avoid invoking `DateFormatSymbols.getZoneStrings()` in `FastDateParser` (logging-log4j2)

2023-11-01 Thread via GitHub
vy commented on PR #1848: URL: https://github.com/apache/logging-log4j2/pull/1848#issuecomment-1788742460 Figured the most recent `FastDateParser` from Apache Commons Lang also still uses `getZoneStrings()`: https://github.com/apache/commons-lang/blob/5b5656a8b403fd91284b0d2acc893dac7ebd5c2

Re: [PR] Upgrade LMAX Disruptor to version 4.0.0 (logging-log4j2)

2023-11-01 Thread via GitHub
ppkarwasz commented on PR #1937: URL: https://github.com/apache/logging-log4j2/pull/1937#issuecomment-1788719530 I would prefer to use the trick I described in #1856. In Disruptor 4.x two things changed: - `EventHandler` has new default methods that come from its previous sub-i

Re: [PR] Upgrade LMAX Disruptor to version 4.0.0 (logging-log4j2)

2023-11-01 Thread via GitHub
tomerarazy commented on PR #1937: URL: https://github.com/apache/logging-log4j2/pull/1937#issuecomment-1788703344 > @tomerarazy, I don't think this will work. See #1829 and [LOG4J2-3595](https://issues.apache.org/jira/browse/LOG4J2-3595). We would appreciate it if you can submit a PR fixing

Re: [PR] Upgrade LMAX Disruptor to version 4.0.0 (logging-log4j2)

2023-11-01 Thread via GitHub
vy commented on PR #1937: URL: https://github.com/apache/logging-log4j2/pull/1937#issuecomment-1788696640 @tomerarazy, I don't think this will work. See #1829 and [LOG4J2-3595](https://issues.apache.org/jira/browse/LOG4J2-3595). We would appreciate it if you can submit a PR fixing the issue

[PR] Upgrade LMAX Disruptor to version 4.0.0 (logging-log4j2)

2023-11-01 Thread via GitHub
tomerarazy opened a new pull request, #1937: URL: https://github.com/apache/logging-log4j2/pull/1937 (no comment) -- 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 unsubsc

Re: [I] notEmpty still outputs text when variable is empty (logging-log4j2)

2023-11-01 Thread via GitHub
vy commented on issue #1922: URL: https://github.com/apache/logging-log4j2/issues/1922#issuecomment-1788650192 @simontankersley, @linhartJ, problem should be fixed by dd4a88ac2e70565e5903a9a397f5f82cacfe. Would you mind giving `2.22.0-SNAPSHOT` a try once [the associated CI run](/apac

Re: [I] notEmpty still outputs text when variable is empty (logging-log4j2)

2023-11-01 Thread via GitHub
vy closed issue #1922: notEmpty still outputs text when variable is empty URL: https://github.com/apache/logging-log4j2/issues/1922 -- 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 commen