> On Jan 10, 2024, at 11:29 AM, Piotr P. Karwasz <piotr.karw...@gmail.com>
> wrote:
>
> Hi Matt,
>
> On Wed, 10 Jan 2024 at 18:45, Matt Sicker <m...@musigma.org> wrote:
>>
>> This might affect 2.x, though it’s largely in the Spring environment
>> property source. Given the application lifecycle there, Spring doesn’t seem
>> to remove its own closed property sources at shutdown, hence the exception.
>> The issue was only reported against Spring 3, though.
>
> A lot of 2.x and 3.x here. ;-)
> What I meant is the patch should be ported to Log4j 2.x, so it can
> work with Spring 3.x. After all Spring is currently using the 2.x
> branch of Log4j.
>
I fixed two bugs. One was reported against 2.x ages ago. The second was first
reported in the Spring issue.
Yes, they can be ported to 2.x but if we release 3.0.0 in the next couple of
months I would prefer to tell users just to upgrade since 3.x specifically
targets the environment Spring 3.x uses.
Ralph
