-Original Message-
From: Piotr P. Karwasz
Sent: Friday, March 15, 2024 9:41 AM
To: Log4J Users List
Subject: Re: Deprecation of Log4j Supplier in 2.x...why?
Hi Jeff,
On Fri, 15 Mar 2024 at 02:43, wrote:
> Our builds are now ***full*** of deprecation warnings. The IDE shows
>
Hi Jeff,
On Fri, 15 Mar 2024 at 02:43, wrote:
> Our builds are now ***full*** of deprecation warnings. The IDE shows
> deprecation highlighting everywhere. Also, CI builds i.e. with Sonar evaluate
> use of deprecated API as Code Smells and Quality Gates fail. When SQ quality
> gates fail
Hi Jeff,
On Fri, 15 Mar 2024 at 07:50, wrote:
> Yes the Javadoc did a fine job of explaining the reason for the change and I
> understood it, but there are so many side-effects from deprecating those
> APIs. My question was more of a "why do this in advance?"
The deprecation was introduced
Hey Piotr,
Thanks for the quick response.
Yes the Javadoc did a fine job of explaining the reason for the change and I
understood it, but there are so many side-effects from deprecating those APIs.
My question was more of a "why do this in advance?"
And, in this case, even when switching
Hi Jeff,
On Fri, 15 Mar 2024 at 02:43, wrote:
> One of the great new features of Log4j2 is the lambda lazy logging.
>
> Since we migrated to Log4j2 we have liberally been trying to take advantage
> of this where we can.
>
> In the last few releases though, in preparation for Log4j 3.x the Log4j
Hello Log4j Team,
One of the great new features of Log4j2 is the lambda lazy logging.
Since we migrated to Log4j2 we have liberally been trying to take advantage of
this where we can.
In the last few releases though, in preparation for Log4j 3.x the Log4j
Supplier has been deprecated without
