Re: A logger config named "root"

On 2024/11/19 18:06:23 "Piotr P. Karwasz" wrote: > Hi Gary, > > On 19.11.2024 17:50, Gary D. Gregory wrote: > > It seems odd to have a logger name not supported in a configuration file > > but then support it programmatically. Did I misread your suggestion? If > > that's the case, then issuing a

Re: A logger config named "root"

Hi Gary, On 19.11.2024 17:50, Gary D. Gregory wrote: It seems odd to have a logger name not supported in a configuration file but then support it programmatically. Did I misread your suggestion? If that's the case, then issuing a warning makes even more sense. The `error` alias works perfect

Re: A logger config named "root"

How much code is it to support "root" fully? If this is trivial, fully supporting "root" makes sense. If not, deprecating it makes sense. Heck, do both! LOL. On Tue, Nov 19, 2024 at 7:11 AM Piotr P. Karwasz wrote: > Hi Gary, > > On 19.11.2024 13:08, Gary Gregory wrote: > > This seems like a nice

Re: A logger config named "root"

Hi Gary, On 19.11.2024 13:08, Gary Gregory wrote: This seems like a nice clean up that will break a lot of configurations. How about we issue a warning in 2.x like "The logger name 'root' is deprecated and will be removed in 3.0"? I thought about going in the other direction: allow users to c

A logger config named "root"

Hi all, In Log4j Core 2 there is a residual support for a logger named "root", e.g.: has the same effect as: However `Configurator.setLevel()`, `Configuration.getLoggerConfig()` and other methods don't support the `root` alias. Should we introduce support for `root` to those methods or ra

Re: A logger config named "root"

Hi Piotr, It seems odd to have a logger name not supported in a configuration file but then support it programmatically. Did I misread your suggestion? If that's the case, then issuing a warning makes even more sense. I don't want to not loose support for "root" (lower-case) in the Log4j 1 con

Re: A logger config named "root"

This seems like a nice clean up that will break a lot of configurations. How about we issue a warning in 2.x like "The logger name 'root' is deprecated and will be removed in 3.0"? Gary On Tue, Nov 19, 2024, 7:01 AM Piotr P. Karwasz wrote: > Hi all, > > In Log4j Core 2 there is a residual sup