Re: [RESULT] Making Log4j 2 API "the Log4j API"

2024-01-22 Thread Piotr P. Karwasz
Hi Matt, On Mon, 22 Jan 2024 at 19:35, Matt Sicker wrote: > > There was also the idea that if we introduce some form of a v3 API, it’ll be > alongside the existing v2 API, not a breaking change. Yes, that idea has also a PoC: https://github.com/apache/logging-log4j2/pull/2215 However right now

Re: [RESULT] Making Log4j 2 API "the Log4j API"

2024-01-22 Thread Matt Sicker
There was also the idea that if we introduce some form of a v3 API, it’ll be alongside the existing v2 API, not a breaking change. > On Jan 21, 2024, at 1:32 PM, Volkan Yazıcı wrote: > > *Abstract:* There will not be a Log4j 3 API. Both Log4j 2 and Log4j 3 will > implement the Log4j 2 API. > >

[RESULT] Making Log4j 2 API "the Log4j API"

2024-01-21 Thread Volkan Yazıcı
*Abstract:* There will not be a Log4j 3 API. Both Log4j 2 and Log4j 3 will implement the Log4j 2 API. In the video call we had with Ralph, Matt, Piotr, Christian, Robert, and I on 2024-01-19 (last Friday), we decided to proceed with this plan. In a nutshell, 1. We will *make the business logic