Hi all,
On Tue, 20 Jun 2023 at 15:13, Matt Sicker wrote:
> As for async logging, if it’s possible to break it into its own module,
> that’d be great, particularly to avoid having to set a system property to
> enable it.
Looking at where `com.lmax:disruptor`, `com.conversantmedia:disruptor`
and
> 1. Configuration has properties related to async logging:
`asyncLoggerConfigDelegate` and `asyncWaitStrategyFactory`. These
should be removed before the split, but I don't know what would be the
right way to do it.
How would that work?
Will Log4j 3 configurations be incompatible with Log4j 2 con
