vy opened a new issue, #2273: URL: https://github.com/apache/logging-log4j2/issues/2273
Currently, Log4j 3 contains a new API (`log4j-api-3.x`) and this is not a good thing. We want to generalize the Log4j 2 API (`log4j-api-2.x`) as _"the Log4j API"_ and use it in Log4j 3 too. (See [the maintainer resolution](https://lists.apache.org/thread/gvk0to32c13xsfz0ytczfs506svx3hxm).) This milestone contributes to that effort. ### Log4j 2 API generalization Log4j 2 API has several parts that are specialized for Log4j 2. This specialization makes it difficult to be a drop-in replacement for Log4j 3 API, which we intend to replace, yet Log4j 3 depends on it with several assumptions. We need to refactor these specialized Log4j 2 API mechanisms such that 1. They are isolated and self-sustained (so that it doesn't matter if they are used in a Log4j 2 or Log4j 3 context) 2. They allow plugging in 3rd party business logic (so that Log4j 2 or Log4j 3 can customize their behaviour as they see fit) - #2249 ### Miscellaneous improvements In accordance with [Boy Scout Rule](https://wiki.c2.com/?BoyScoutRule), things we have improved along the way: - #2266 -- 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...@logging.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
