Ralph Goers

Lack of an answer is an answer.

I am going to go one further. This is NOT a bug. The purpose of ContextDataProvider is to inject data into LogEvents. That is documented clearly in the [Extending Log4j](https://logging.apache.org/log4j/2.x/manual/extending.html)...

Well, I am going to reopen this as PR https://github.com/apache/logging-log4j2/pull/2438 actually fixes this.

We have not released 2.24.0 yet. You can try with the latest SNAPSHOT

@ppkarwasz @vy I agree that the below is not ideal or what I would recommend but the exception does need be logged as a parameter. Changing this behavior now under...

I use a profile to generate pdf's. So when I do -P pdf it uses that configuration and ignores the default. It would be great if I could specify a...

The proper way to change this is to change the copyright line from ``` Copyright 2011-2022 The Apache Software Foundation ``` to ``` Copyright 2011-Present The Apache Software Foundation ```...

I am not sure how to apply this if your own compiles and unit tests failed.

I just saw this and will look into whether this can be addressed in Log4j itself. I am seeing a different, but related, error when shutting down a sample Spring...

I have a fix for this in Log4j that I am testing. It simply catches the exception and ignores the PropertySource. However, testing has been difficult as I am trying...