Re: [log4j] ProGuard support in `log4j-api`

It feels wrong to add support for a special development time tool in our runtime. Gary On Thu, Jan 11, 2024, 1:58 PM Ralph Goers wrote: > Yeah - if we add it to the code base that implies that we are testing it. > I really don’t want to be in the position where we start adding > customizations

Re: Spring 3 and Log4j 3

On 2024/01/10 09:27:22 Volkan Yazıcı wrote: > Thanks for chasing this Ralph, it is indeed a nice step forwards. > > The aforementioned Log4j issue is fixed in #2062 > : > >1. You submitted the PR on Dec 5 at 04:15 (GMT+1) and merged it

Re: [log4j] ProGuard support in `log4j-api`

Yeah - if we add it to the code base that implies that we are testing it. I really don’t want to be in the position where we start adding customizations for every tool a user might be using. This is very much in line with our not wanting to keep adding more and more integrations . Ralph > On

[log4j] ProGuard support in `log4j-api`

ProGuard – a GPL2-licensed, widely used JAR optimizer and obfuscator in the Android world – doesn't work with `log4j-api` out of the box. In summary, since Log4j uses reflection, ProGuard needs to be configured to avoid removing certain Log4j classes. A

[VOTE][LAZY] Release Apache Logging Parent 10.6.0 RC1

This is a lazy-vote to release the Apache Logging Parent 10.6.0. Website: https://logging.staged.apache.org/logging-parent GitHub: https://github.com/apache/logging-parent Commit: 64ae84e05803f3ab6d4201512b00f1cb1c4051e8 Distribution: https://dist.apache.org/repos/dist/dev/logging/logging-parent

Re: Removal of `log4j-jcl` in `3.x`

+1 Piotr, you populated #2163 tasks last week and there asked to port `log4j-jcl` changes from `2.x` to `main`. That is what I spent my yesterday with. I would appreciate it if you can share these kinds of developments earlier. Putting that