Hello Gurumoorthi,
Piotr already responded to your email:
> MapLookup#newMap changed from private (as in 2.2) to package (as in
> 2.17.1) in the course of history. Your Tomcat is picking up the
> private one, which means that log4j-core-2.2.jar is still on the
> classpath.
> Double check that
That doesn’t really work:
1. As soon as there is some bug in it means someone has to go an create the
repo and the appropriate scaffolding to get a release to work. No one will ever
do it.
2. I release cannot consists of stuff from multiple repos. The distribution zip
needs to contain
Hi Ralph,
On Mon, 20 Mar 2023 at 15:09, Apache wrote:
>
> I would be comfortable with this if it is moved to its own repo and released
> first, then removed from the Log4J repo. I am not comfortable with “we can do
> it someday if we want to” unless we are dropping support for it.
Can we keep
Hi Team,
Can you please help us to fix this issue.
Regards,
Guru.
From: Dominik Psenner
Sent: 04 March 2023 02:16
To: secur...@logging.apache.org
Cc: Paolo Gil Ostrea ; Roark Hamilton
; Gurumoorthi Vijayalingam
Subject: [External] Re: Log4j Issue
CAUTION: This message was sent from outside
I do not speak English, so please excuse the machine translation.
Hello.
Thank you for your quick reply.
> There should be a branch containing the work in progress of the next
> generation rolling file appender.
> I named it something like RFA-NG if my memory does not fail on me.
> You could
I would be comfortable with this if it is moved to its own repo and released
first, then removed from the Log4J repo. I am not comfortable with “we can do
it someday if we want to” unless we are dropping support for it.
Ralph
> On Mar 20, 2023, at 3:36 AM, Volkan Yazıcı wrote:
>
> [TLDR:
[TLDR: Piotr and I propose moving `log4j-jmx-gui` to its own repository to
ease Java 9+ migration for `2.x`, objections?]
In the `2.x` branch, AFAIK, `log4j-jmx-gui` is the only module that has a
Java 8 requirement, i.e., `jconsole.jar`. Piotr and I have been trying to
come up with ways to make
