Renaming `log4j-core`

Hi all, I think one of the main problems preventing Log4j API from being used more wildly are naming problems and misinformation on many sites. Personally I find the name `log4j-core` for our implementation quite unfortunate: this is often interpreted as "core Log4j classes", which suggests that

Re: [I] Drop or move JANSI support (logging-log4j2)

But is it enabled in cmd.exe? Windows Terminal is a separate download, at least on Windows 10. Gary On Thu, Jun 22, 2023, 03:55 ppkarwasz (via GitHub) wrote: > > ppkarwasz opened a new issue, #1529: > URL: https://github.com/apache/logging-log4j2/issues/1529 > >Since microsoft/terminal#2824

Re: Renaming `log4j-core`

I'm all for it. Finding a good new name is challenging, sure "impl" seems obvious, but maybe this is where slf4j/logback can be a lesson with it's clear split. Having a separate site for the API only might help. Gary On Thu, Jun 22, 2023, 04:35 Piotr P. Karwasz wrote: > Hi all, > > I think one

Re: [I] Drop or move JANSI support (logging-log4j2)

Hi Gary, On Thu, 22 Jun 2023 at 12:05, Gary Gregory wrote: > > But is it enabled in cmd.exe? Windows Terminal is a separate download, at > least on Windows 10. You are right: removing the 'HKEY_CURRENT_USER\Console\VirtualTerminalLevel' on my system disabled ANSI escapes, so the default value fo

Re: [I] Drop or move JANSI support (logging-log4j2)

On Thu, Jun 22, 2023 at 7:06 AM Piotr P. Karwasz wrote: > > Hi Gary, > > On Thu, 22 Jun 2023 at 12:05, Gary Gregory wrote: > > > > But is it enabled in cmd.exe? Windows Terminal is a separate download, at > > least on Windows 10. > > You are right: removing the > 'HKEY_CURRENT_USER\Console\Virtua

Re: [I] Drop or move JANSI support (logging-log4j2)

On Thu, Jun 22, 2023 at 7:19 AM Gary Gregory wrote: > > On Thu, Jun 22, 2023 at 7:06 AM Piotr P. Karwasz > wrote: > > > > Hi Gary, > > > > On Thu, 22 Jun 2023 at 12:05, Gary Gregory wrote: > > > > > > But is it enabled in cmd.exe? Windows Terminal is a separate download, at > > > least on Window

Re: Renaming `log4j-core`

Pretend for a moment that you work for a company that has lots of shared components that don’t always do everything correctly and publish artifacts that declare a dependency on log4j-core (Note: I do). If we change the name of log4j-core to something else then suddenly both an older version of

[log4j] Separate BOM releases

Piotr and I have been contemplating moving Log4j BOM to its separate repository with its own release cycle. This need will become even more pressing as we start breaking down the Log4j modules to their own repository. Ralph and Piotr already exchanged some ideas in #1526