ppkarwasz commented on issue #3775:
URL:
https://github.com/apache/logging-log4j2/issues/3775#issuecomment-3092156782
Hi @yybmion,
> ```java
> public static String[] getSupportedConfigurationExtensions() {
> final List extensions = new ArrayList<>();
> for (final Conf
rschmitt opened a new issue, #3836:
URL: https://github.com/apache/logging-log4j2/issues/3836
## Description
A bad Log4j2 properties file will cause an exception to be thrown from
`PropertiesConfigurationBuilder`, whereas previous versions would fall back to
the default logging confi
rschmitt opened a new issue, #3835:
URL: https://github.com/apache/logging-log4j2/issues/3835
## Description
The default logging configuration in `log4j-core` has clearly regressed,
with newlines no longer being emitted.
## Configuration
**Version:** 2.25.0 and 2.25.1
github-actions[bot] merged PR #209:
URL: https://github.com/apache/logging-log4j-transform/pull/209
--
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: noti
github-actions[bot] merged PR #208:
URL: https://github.com/apache/logging-log4j-transform/pull/208
--
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: noti
jhl221123 commented on PR #3831:
URL: https://github.com/apache/logging-log4j2/pull/3831#issuecomment-308978
Hi @ppkarwasz,
Thank you for the feedback and the very kind words! I've added the changelog
entry as requested.
I'm honored by the offer to connect and discuss getti
ringchenhao commented on issue #263:
URL:
https://github.com/apache/logging-log4net/issues/263#issuecomment-3088810169
> Hi, I can try. Can you upload the code and binaries for repro?
Help~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, pl
rob975 opened a new pull request, #352:
URL: https://github.com/apache/logging-log4j-samples/pull/352
This is a PR that addresses
https://github.com/apache/logging-log4j2/issues/3834#issuecomment-3085025523.
Command:
```
mvn -X package -pl :log4j-assembly-test -am
```
will sho
yybmion commented on issue #3775:
URL:
https://github.com/apache/logging-log4j2/issues/3775#issuecomment-3088337699
Thanks for guidance @ppkarwasz!
Based on the discussion above, I'm proposing to add this static method to
ConfigurationFactory
```java
/**
* Returns configuration
ppkarwasz commented on issue #3834:
URL:
https://github.com/apache/logging-log4j2/issues/3834#issuecomment-3085025523
Hi @rob975,
It turns out the fix for the `error_prone` issue was ineffective due to an
oversight on my part (see #3822).
The core problem is that we don’t currentl
ppkarwasz commented on issue #3704:
URL:
https://github.com/apache/logging-log4j2/issues/3704#issuecomment-3084857545
Hi @sidhantmourya,
> I'm now looking at how to implement PatternLayout support for headers
similar to how SubjectSerializer works.
>
https://github.com/apache/l
rob975 opened a new issue, #3834:
URL: https://github.com/apache/logging-log4j2/issues/3834
## Description
Last week I opened issue #3813 and tested the release candidate for version
`2.25.1` as suggested. It worked fine.
Today I upgraded to version `2.25.1` and the issue is not so
sidhantmourya commented on issue #3704:
URL:
https://github.com/apache/logging-log4j2/issues/3704#issuecomment-3084605338
Hi @ppkarwasz,
After reading through the documentation, I've updated the header handling to
properly encode and fold values per RFC 5322 requirements. The current
im
ppkarwasz commented on PR #3831:
URL: https://github.com/apache/logging-log4j2/pull/3831#issuecomment-3084175593
Hi @jhl221123,
Could you please add a changelog entry to this PR? While it's just a
one-liner, it addresses a concrete issue reported by a user and deserves to be
document
ppkarwasz opened a new issue, #3832:
URL: https://github.com/apache/logging-log4j2/issues/3832
The current `log4j-core-test` module includes a variety of test fixtures
primarily designed to test Log4j Core itself and its internal plugins. These
fixtures assume that:
* Static loggers
ringchenhao commented on issue #263:
URL:
https://github.com/apache/logging-log4net/issues/263#issuecomment-3082626734
Create a .NET 8.0 console application with the following main code, then
publish the program with the "Generate single file" option enabled. When
executing the published p
ringchenhao commented on issue #263:
URL:
https://github.com/apache/logging-log4net/issues/263#issuecomment-3082620760
App.config :
ringchenhao commented on issue #263:
URL:
https://github.com/apache/logging-log4net/issues/263#issuecomment-3082612491
using log4net;
using log4net.Config;
[assembly: XmlConfigurator(Watch = true)]
namespace Log4NetExample
{
internal class Program
{
swebb2066 merged PR #511:
URL: https://github.com/apache/logging-log4cxx/pull/511
--
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: notifications-unsubscr
github-actions[bot] commented on PR #3831:
URL: https://github.com/apache/logging-log4j2/pull/3831#issuecomment-3080201580
Job
Requested goals
Build Tool Version
Build Outcome
Build Scan®
build-
github-actions[bot] merged PR #207:
URL: https://github.com/apache/logging-log4j-transform/pull/207
--
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: noti
ppkarwasz commented on issue #3704:
URL:
https://github.com/apache/logging-log4j2/issues/3704#issuecomment-3080017458
Hi @sidhantmourya,
Thanks for digging into this!
I must admit that when I introduced the Jakarta version of the SMTP
appender, I only added a minimal abstracti
ppkarwasz commented on issue #3779:
URL:
https://github.com/apache/logging-log4j2/issues/3779#issuecomment-3079567495
Hi @recaph,
Thanks for reporting this!
The message you're seeing appears to be generated by the [Spring Dependency
Management
Plugin](https://docs.spring.io/s
sidhantmourya commented on issue #3704:
URL:
https://github.com/apache/logging-log4j2/issues/3704#issuecomment-3079210657
@ppkarwasz I'm adding custom header support to the SMTP appender similar to
the HTTP appender, but need guidance on handling the javax.mail vs jakarta.mail
MimeMessage
recaph commented on issue #3779:
URL:
https://github.com/apache/logging-log4j2/issues/3779#issuecomment-3078816844
getting similar error with log4j 2.25.1 and Spring Boot 2.7
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub an
jhl221123 opened a new pull request, #3831:
URL: https://github.com/apache/logging-log4j2/pull/3831
The debug log message in `AbstractDriverManagerConnectionSource` had 4
placeholders but was supplied with 5 arguments. This corrects the format string
to match the argument count, resolving t
ringchenhao closed issue #263: Produce single file
URL: https://github.com/apache/logging-log4net/issues/263
--
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-m
ringchenhao commented on issue #263:
URL:
https://github.com/apache/logging-log4net/issues/263#issuecomment-3077336674
I have identified that this issue is related to another third-party library,
SystemCore. When using log4net alone, the verification passes successfully, and
logs are gener
gdziadkiewicz commented on issue #263:
URL:
https://github.com/apache/logging-log4net/issues/263#issuecomment-3076717649
Hi, I can try. Can you upload the code and binaries for repro?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
swebb2066 commented on code in PR #511:
URL: https://github.com/apache/logging-log4cxx/pull/511#discussion_r2209155149
##
src/examples/cpp/MyApp1.cpp:
##
@@ -20,5 +20,6 @@ int main(int argc, char **argv) {
LOG4CXX_INFO(logger, "Entering application.");
foo();
swebb2066 commented on code in PR #511:
URL: https://github.com/apache/logging-log4cxx/pull/511#discussion_r2209155149
##
src/examples/cpp/MyApp1.cpp:
##
@@ -20,5 +20,6 @@ int main(int argc, char **argv) {
LOG4CXX_INFO(logger, "Entering application.");
foo();
swebb2066 commented on code in PR #511:
URL: https://github.com/apache/logging-log4cxx/pull/511#discussion_r2209109613
##
src/examples/cpp/MyApp1.cpp:
##
@@ -20,5 +20,6 @@ int main(int argc, char **argv) {
LOG4CXX_INFO(logger, "Entering application.");
foo();
swebb2066 commented on code in PR #511:
URL: https://github.com/apache/logging-log4cxx/pull/511#discussion_r2209107114
##
src/examples/cpp/MyApp1.cpp:
##
@@ -1,11 +1,11 @@
-#include
+#include
#include
-static auto logger = log4cxx::Logger::getLogger("MyApp");
Review Comme
rm5248 commented on code in PR #511:
URL: https://github.com/apache/logging-log4cxx/pull/511#discussion_r2209095595
##
src/examples/cpp/MyApp1.cpp:
##
@@ -1,11 +1,11 @@
-#include
+#include
#include
-static auto logger = log4cxx::Logger::getLogger("MyApp");
Review Comment:
ringchenhao opened a new issue, #263:
URL: https://github.com/apache/logging-log4net/issues/263
When publishing a C# application with .NET 8.0 framework, if the "Produce
single file" option is enabled in the publish settings, testing the generated
EXE reveals that neither the log folder nor
swebb2066 commented on issue #510:
URL:
https://github.com/apache/logging-log4cxx/issues/510#issuecomment-3076461698
Your application must call `LogManager::shutdown` when it exits
to prevent undefined behaviour when using this appender.
I have updated the documentation in #511
-
kurtostfeld commented on PR #3701:
URL: https://github.com/apache/logging-log4j2/pull/3701#issuecomment-3075170184
@ppkarwasz awesome. I suspected it was a flaky test. thank you. If there are
issues with the Jackson 3.0 upgrade, I'd like to help investigate and resolve
them. I use log4j on
ppkarwasz opened a new issue, #3828:
URL: https://github.com/apache/logging-log4j2/issues/3828
### Discussed in https://github.com/apache/logging-log4j2/discussions/3827
Originally posted by **RichMacDonald** July 15, 2025
Version 2.24.3
org.apache.logging.log4j.core.ap
MartyIX commented on PR #350:
URL:
https://github.com/apache/logging-log4j-samples/pull/350#issuecomment-3074490645
That's great insight! I opened #351 which reports the error.
I'm closing this PR.
--
This is an automated message from the Apache Git Service.
To respond to the mess
MartyIX closed pull request #350: Gradle: Add `buildSrc` to the sample project
URL: https://github.com/apache/logging-log4j-samples/pull/350
--
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 specif
MartyIX opened a new pull request, #351:
URL: https://github.com/apache/logging-log4j-samples/pull/351
This is a PR that addresses
https://github.com/apache/logging-log4j-samples/pull/350#issuecomment-3069913098.
Now, this command
```
export LOG4J_VERSION=2.25.1; ./gradlew :
swebb2066 opened a new pull request, #511:
URL: https://github.com/apache/logging-log4cxx/pull/511
When the application does not call LogManager::shutdown before program exit,
the single LogLog instance is destroyed before AsynAppender terminates.
Undefined behaviour (use-after-free) arises
ppkarwasz commented on PR #350:
URL:
https://github.com/apache/logging-log4j-samples/pull/350#issuecomment-3069913098
Hi @MartyIX,
Thanks again for digging into this — even negative results are valuable, as
they help us identify what might be missing in the test project.
Based
github-actions[bot] merged PR #81:
URL: https://github.com/apache/logging-log4j-audit-sample/pull/81
--
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: not
dependabot[bot] opened a new pull request, #81:
URL: https://github.com/apache/logging-log4j-audit-sample/pull/81
[ caused by the use of a thread-local `LogBuilder`
pool.
The leak occurred because th
mordio commented on issue #260:
URL:
https://github.com/apache/logging-log4net/issues/260#issuecomment-3069116897
FYI: I am using `.NET Framework v4.8` for the project using log4net. So I
can confirm it works for that version.
--
This is an automated message from the Apache Git Service.
gmiscione commented on issue #3819:
URL:
https://github.com/apache/logging-log4j2/issues/3819#issuecomment-3068154118
I am no expert in low latency programming, but the use case you are
describing makes perfect sense. I don't know if Logback has support for
something similar to this poolin
RK-BFX commented on issue #510:
URL:
https://github.com/apache/logging-log4cxx/issues/510#issuecomment-3068025007
I'll submit a PR with a fix soon.
--
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 t
RK-BFX opened a new issue, #510:
URL: https://github.com/apache/logging-log4cxx/issues/510
**General:** I build Log4cxx from sources in macOS with
`LOG4CXX_MULTIPROCESS_ROLLING_FILE_APPENDER=on` with all dependencies linked
statically in order to avoid adding any dylib (DSO) dependencies, b
ppkarwasz commented on issue #3819:
URL:
https://github.com/apache/logging-log4j2/issues/3819#issuecomment-3067246866
> Just out of curiosity, what is exactly the use case for the pooling of
those builders? When are they supposed to be used?
We have some users in latency-sensitive do
ppkarwasz commented on issue #3704:
URL:
https://github.com/apache/logging-log4j2/issues/3704#issuecomment-3067242002
Hi @sidhantmourya,
Thanks for volunteering! We really appreciate contributions — all issues are
open for community help, especially since we receive more requests tha
sidhantmourya commented on issue #3704:
URL:
https://github.com/apache/logging-log4j2/issues/3704#issuecomment-3067226687
Hello @ppkarwasz ,
I'd like to contribute to this enhancement.
Is this issue currently open for contribution? If so, could you please guide
me on where to
gmiscione commented on issue #3819:
URL:
https://github.com/apache/logging-log4j2/issues/3819#issuecomment-3067120765
Hi, @ppkarwasz,
first of all, thank you for having acknowledged the issue. I have to be
honest and admit that I am no expert in the Logback world, I am just a user of
th
ppkarwasz commented on issue #3697:
URL:
https://github.com/apache/logging-log4j2/issues/3697#issuecomment-3067064984
Hi @Class-New,
Apologies for the delayed response — we're doing our best to respond to all
issues despite limited time, but occasionally some slip through the cracks.
ppkarwasz commented on issue #3779:
URL:
https://github.com/apache/logging-log4j2/issues/3779#issuecomment-3067057529
> I can try to carve out some time but my understanding of Gradle and its
dependency system is pretty basic.
That would be very much appreciated! As you can probably
ppkarwasz commented on issue #3819:
URL:
https://github.com/apache/logging-log4j2/issues/3819#issuecomment-3067054551
Hi @gmiscione,
Great catch — thanks for reporting this! :100:
I see two possible approaches to address the issue:
1. **Fix the misuse of `ThreadLocal`**
ppkarwasz commented on PR #2249:
URL: https://github.com/apache/logging-log4j2/pull/2249#issuecomment-3067027459
Hi @vy,
It looks like this change isn't mentioned in the [2.23.0 release
notes](https://logging.apache.org/log4j/2.x/release-notes.html#release-notes-2-23-0),
even though—
ppkarwasz commented on PR #3789:
URL: https://github.com/apache/logging-log4j2/pull/3789#issuecomment-3066741660
> @ppkarwasz, consider users having their custom instant formatters, some
might even be relying on `{Fixed,Fast}DateFormat`. They will get excited about
`NamedInstantPattern`, wi
ppkarwasz commented on code in PR #3789:
URL: https://github.com/apache/logging-log4j2/pull/3789#discussion_r2203224449
##
log4j-core/src/main/java/org/apache/logging/log4j/core/pattern/NamedInstantPattern.java:
##
@@ -0,0 +1,163 @@
+/*
+ * Licensed to the Apache Software Founda
MartyIX commented on issue #3779:
URL:
https://github.com/apache/logging-log4j2/issues/3779#issuecomment-3065627433
> Since this issue cannot be detected by our current [Gradle Integration
Test](https://github.com/apache/logging-log4j-samples/tree/main/log4j-samples-gradle-metadata),
would
ppkarwasz commented on issue #3779:
URL:
https://github.com/apache/logging-log4j2/issues/3779#issuecomment-3065139812
Hi @MartyIX,
Thank you for the detailed feedback.
The resolution of the `com.google.errorprone:error_prone_annotations`
dependency in the **consumer** POM (as
ppkarwasz opened a new issue, #3822:
URL: https://github.com/apache/logging-log4j2/issues/3822
Unfortunately, PR #3785 did **not** resolve #3779. I mistakenly applied the
new `error-prone-annotations.version` property only to the Gradle Module
Metadata plugin configuration:
https://
ppkarwasz commented on PR #3785:
URL: https://github.com/apache/logging-log4j2/pull/3785#issuecomment-3065118310
Unfortunately, this PR did **not** resolve #3779. I mistakenly applied the
new `error-prone-annotations.version` property only to the Gradle Module
Metadata plugin configuration:
MartyIX commented on issue #3779:
URL:
https://github.com/apache/logging-log4j2/issues/3779#issuecomment-3064916603
I tried upgrading to 2.25.1 (released today) and I still see
```
> Task :buildSrc:jar
Errors occurred while building effective model from
/Users/myuser/.gradle/c
swebb2066 merged PR #509:
URL: https://github.com/apache/logging-log4cxx/pull/509
--
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: notifications-unsubscr
github-actions[bot] merged PR #206:
URL: https://github.com/apache/logging-log4j-transform/pull/206
--
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: noti
github-actions[bot] merged PR #46:
URL: https://github.com/apache/logging-log4j-jmx-gui/pull/46
--
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: notifica
ppkarwasz opened a new pull request, #3820:
URL: https://github.com/apache/logging-log4j2/pull/3820
This change merges the changelog changes performed during the release of
`2.25.1` back into the `2.x` branch.
--
This is an automated message from the Apache Git Service.
To respond to the
gmiscione opened a new issue, #3819:
URL: https://github.com/apache/logging-log4j2/issues/3819
## Description
We have a web application packaged as a .war file deployed in Tomcat 11. The
web application uses logback as the main logger and slf4j as a facade. Then we
use log4j-to-slf4j
ppkarwasz commented on issue #3816:
URL:
https://github.com/apache/logging-log4j2/issues/3816#issuecomment-3062039237
Hi @vy,
> As reported by [@ppkarwasz](https://github.com/ppkarwasz) (see [the review
discussion](https://github.com/apache/logging-log4j2/pull/3789#discussion_r219787
vy commented on code in PR #3789:
URL: https://github.com/apache/logging-log4j2/pull/3789#discussion_r2200247276
##
log4j-core/src/main/java/org/apache/logging/log4j/core/pattern/NamedInstantPattern.java:
##
@@ -0,0 +1,163 @@
+/*
+ * Licensed to the Apache Software Foundation (A
vy commented on PR #3789:
URL: https://github.com/apache/logging-log4j2/pull/3789#issuecomment-3061510068
@ppkarwasz, consider users having their custom instant formatters, some
might even be relying on `{Fixed,Fast}DateFormat`. They will get excited about
`NamedInstantPattern`, will try to
vy commented on code in PR #3789:
URL: https://github.com/apache/logging-log4j2/pull/3789#discussion_r2200140855
##
log4j-core/src/main/java/org/apache/logging/log4j/core/util/internal/instant/InstantPatternLegacyFormatter.java:
##
@@ -46,7 +46,10 @@ final class InstantPatternLe
vy opened a new issue, #3816:
URL: https://github.com/apache/logging-log4j2/issues/3816
`InstantPatternLegacyFormatter` uses `InstantPatternDynamicFormatter` to
determine the precision of the *legacy* date & time pattern it receives. As
reported by @ppkarwasz (see [the review
discussion](h
yogitasingh001 commented on PR #253:
URL: https://github.com/apache/logging-log4net/pull/253#issuecomment-3060179923
Ok @FreeAndNil i will test and update. Sorry for the late response
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
swebb2066 opened a new pull request, #509:
URL: https://github.com/apache/logging-log4cxx/pull/509
This PR applies [this stack overflow
advise](https://stackoverflow.com/questions/3961505/how-can-i-escape-double-quotes-in-xml-attributes-values/47534887#47534887)
when replacing a double quot
github-actions[bot] merged PR #205:
URL: https://github.com/apache/logging-log4j-transform/pull/205
--
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: noti
ppkarwasz commented on issue #3770:
URL:
https://github.com/apache/logging-log4j2/issues/3770#issuecomment-3058064656
Hi @mmoayyed,
Please see #3766, I will likely close the vote tomorrow, so there is still a
chance to check the release candidate before the official release.
--
Th
mmoayyed commented on issue #3770:
URL:
https://github.com/apache/logging-log4j2/issues/3770#issuecomment-3058017667
Hello all, apologies for resurrecting this thread; is this fix still
planned for 2.25.1? I see the milestone date was set to July 6th, and the
release is 4 days due. This i
ppkarwasz commented on code in PR #3789:
URL: https://github.com/apache/logging-log4j2/pull/3789#discussion_r2197893975
##
log4j-core/src/main/java/org/apache/logging/log4j/core/pattern/NamedInstantPattern.java:
##
@@ -0,0 +1,163 @@
+/*
+ * Licensed to the Apache Software Founda
ppkarwasz commented on code in PR #3789:
URL: https://github.com/apache/logging-log4j2/pull/3789#discussion_r2197874778
##
log4j-core/src/main/java/org/apache/logging/log4j/core/util/internal/instant/InstantPatternLegacyFormatter.java:
##
@@ -46,7 +46,10 @@ final class InstantPa
vy commented on code in PR #3789:
URL: https://github.com/apache/logging-log4j2/pull/3789#discussion_r2197547461
##
log4j-core/src/main/java/org/apache/logging/log4j/core/pattern/NamedInstantPattern.java:
##
@@ -0,0 +1,163 @@
+/*
+ * Licensed to the Apache Software Foundation (A
ppkarwasz closed issue #3813: failed to build parent project warning
URL: https://github.com/apache/logging-log4j2/issues/3813
--
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.
T
ppkarwasz commented on issue #3813:
URL:
https://github.com/apache/logging-log4j2/issues/3813#issuecomment-3056347491
Hi @rob975,
Thanks for reporting this. The issue you're encountering is most likely
caused by #3758 and #3779.
We’ve prepared a release candidate for `2.25.1`,
ppkarwasz commented on code in PR #3789:
URL: https://github.com/apache/logging-log4j2/pull/3789#discussion_r2196942219
##
log4j-core/src/main/java/org/apache/logging/log4j/core/pattern/DatePatternConverter.java:
##
@@ -109,40 +109,19 @@ private static String readPattern(@Nullab
rob975 opened a new issue, #3813:
URL: https://github.com/apache/logging-log4j2/issues/3813
## Description
When running maven-assembly-plugin we get these warnings
```
[WARNING] Failed to build parent project for
org.apache.logging.log4j:log4j-layout-template-json:jar:2.25.0
ppkarwasz commented on code in PR #3789:
URL: https://github.com/apache/logging-log4j2/pull/3789#discussion_r2196829985
##
log4j-core/src/main/java/org/apache/logging/log4j/core/pattern/DatePatternConverter.java:
##
@@ -109,40 +109,19 @@ private static String readPattern(@Nullab
ringchenhao commented on issue #260:
URL:
https://github.com/apache/logging-log4net/issues/260#issuecomment-3055976305
i have faced the same problem with mordio, it is ok with the platform .net
8.0, but with platform .net 4.6.2, it shows the same error print like mordio
--
This is an aut
vy commented on code in PR #3789:
URL: https://github.com/apache/logging-log4j2/pull/3789#discussion_r2196798155
##
log4j-core/src/main/java/org/apache/logging/log4j/core/pattern/DatePatternConverter.java:
##
@@ -109,40 +109,19 @@ private static String readPattern(@Nullable fina
ppkarwasz commented on code in PR #3789:
URL: https://github.com/apache/logging-log4j2/pull/3789#discussion_r2196109011
##
log4j-core/src/main/java/org/apache/logging/log4j/core/pattern/DatePatternConverter.java:
##
@@ -109,40 +109,19 @@ private static String readPattern(@Nullab
github-actions[bot] commented on PR #3812:
URL: https://github.com/apache/logging-log4j2/pull/3812#issuecomment-3054240664
Job
Requested goals
Build Tool Version
Build Outcome
Build Scan®
build-
vy commented on code in PR #3789:
URL: https://github.com/apache/logging-log4j2/pull/3789#discussion_r2196059297
##
log4j-core/src/main/java/org/apache/logging/log4j/core/pattern/DatePatternConverter.java:
##
@@ -109,40 +109,19 @@ private static String readPattern(@Nullable fina
ppkarwasz commented on PR #3789:
URL: https://github.com/apache/logging-log4j2/pull/3789#issuecomment-3053765302
> In its current state, deprecated formatters are an island – no
programmatic connections from anywhere. We can safely delete them, yet keep the
legacy formatters configuration k
vy closed issue #3809: ThrowablePatternConverter deprecated constructors refer
to a package private constructor
URL: https://github.com/apache/logging-log4j2/issues/3809
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
vy commented on issue #3809:
URL:
https://github.com/apache/logging-log4j2/issues/3809#issuecomment-3053684326
@snicoll, submitted spring-projects/spring-boot#46372, closing this issue.
Please feel free to comment and/or re-open if you have further concerns.
--
This is an automated messa
1 - 100 of 5637 matches
Mail list logo
