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 replacement. I get why you did this, but ... "why?" did you do this? 😁 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 our downstream jobs don't trigger. I read Hibernate did something similar to indicate "intent" without replacement, but they ultimately ended up reverting that change. Cheers, Jeff
