logging-log4j2
logging-log4j2 copied to clipboard
apache
Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.
Bumps org.apache.commons:commons-compress from 1.25.0 to 1.26.0. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Bumps [co.elastic.logging:log4j2-ecs-layout](https://github.com/elastic/ecs-logging-java) from 1.5.0 to 1.6.0. Commits 06ca554 Await artifact on maven central on release (#236) 8ee34b9 Switch to nexus plugin for releases (#235) 8344327 fix: don't forget permissions (#232)...
In order for Log4j Core 3.x not to depend on the utility classes in Log4j API 2.x, we provide a new `AbstractLogger` in `log4j-sdk`. The main improvements to this `AbstractLogger`...
Bumps org.apache.commons:commons-compress from 1.25.0 to 1.26.0. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a...
### Discussed in https://github.com/apache/logging-log4j2/discussions/1842 Originally posted by **RollsCorey** October 6, 2023 Hello. Using log4j 2.20.0. My configuration file specifies a SizeBasedTriggeringPolicy and a TimeBasedTriggeringPolicy. My understanding is that when the...
In order to concentrate our limited resources on the remaining modules, the PMC decided to deprecate the following modules/features in 2.x and to remove them in 3.x: * `log4j-cassandra`, *...
As shown in [this user report](https://lists.apache.org/thread/ynxrn9vsmdqs31jrml71xb582o7m74qf), linkage errors with the LMAX Disruptor library never end up in the status log. We should add more debugging there to allow users to...
Following the conclusion of #2273, we continue our goal of rebasing Log4j Core 3.x on top of Log4j API 2.x. In order to do so we need to: - [...
This adds a single `StatusConsoleListener` that is registered by the first Log4j Core configuration active and removed by the last one. Compare to the current status this: 1. Prevents users...
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...
