Re: [log4cxx] Board report entry

[Stephen Webb]

To make it a positive statement, I would report

As a result of the result of work since the 1.2 release in January,
benchmark performance measurements show upto 60% reduction in overhead
in Log4cxx internals.


On Wed, May 1, 2024 at 1:06 AM Robert Middleton 
wrote:

> There's nothing major going on at the moment, just some various
> improvements to the code to make it more efficient.  I'm not sure if
> Stephen has anything else to add.
>
> -Robert Middleton
>
> On Tue, Apr 30, 2024 at 10:21 AM Volkan Yazıcı  wrote:
> >
> > Can a Log4cxx maintainer share what is getting cooked since March 20,
> > please? A short summary of 3-4 sentences would suffice. See the past
> reports
> >  for
> > inspiration.
>

Re: Use of java.beans in log4j-core

[Stig Rohde Døssing]

Please disregard, I see this was already done in
https://github.com/apache/logging-log4j2/commit/b3c13758ccd68ace56bf1a398f05af9862dbcc2c
.

Den tirs. 30. apr. 2024 kl. 17.45 skrev Stig Rohde Døssing <
stigdoess...@gmail.com>:

> Hi.
>
> LoggerContext contains references to java.beans due to the use of a few
> listener-related classes, which are exposed in the API of LoggerContext.
>
>
> https://github.com/apache/logging-log4j2/blob/6219e667fdc5aa19e23b699b5eb82dd6d9c61691/log4j-core/src/main/java/org/apache/logging/log4j/core/LoggerContext.java#L23
>
> Would it be possible to replace these classes with log4j specific variants
> some future version, or is breaking the API of LoggerContext a non-starter?
>
> I'm asking because java.beans is part of the java.desktop module of the
> JDK, which means the use of these two classes in LoggerContext prevents
> stripping out 35MB of UI-related classes from the JDK when creating a
> custom runtime image via jlink, which seems unfortunate.
>

Use of java.beans in log4j-core

[Stig Rohde Døssing]

Hi.

LoggerContext contains references to java.beans due to the use of a few
listener-related classes, which are exposed in the API of LoggerContext.

https://github.com/apache/logging-log4j2/blob/6219e667fdc5aa19e23b699b5eb82dd6d9c61691/log4j-core/src/main/java/org/apache/logging/log4j/core/LoggerContext.java#L23

Would it be possible to replace these classes with log4j specific variants
some future version, or is breaking the API of LoggerContext a non-starter?

I'm asking because java.beans is part of the java.desktop module of the
JDK, which means the use of these two classes in LoggerContext prevents
stripping out 35MB of UI-related classes from the JDK when creating a
custom runtime image via jlink, which seems unfortunate.

Re: [log4cxx] Board report entry

[Robert Middleton]

There's nothing major going on at the moment, just some various
improvements to the code to make it more efficient.  I'm not sure if
Stephen has anything else to add.

-Robert Middleton

On Tue, Apr 30, 2024 at 10:21 AM Volkan Yazıcı  wrote:
>
> Can a Log4cxx maintainer share what is getting cooked since March 20,
> please? A short summary of 3-4 sentences would suffice. See the past reports
>  for
> inspiration.

[log4cxx] Board report entry

[Volkan Yazıcı]

Can a Log4cxx maintainer share what is getting cooked since March 20,
please? A short summary of 3-4 sentences would suffice. See the past reports
 for
inspiration.