You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Matt Sicker (Jira)" <ji...@apache.org> on 2022/10/31 01:27:00 UTC

[jira] [Resolved] (LOG4J2-3459) Reduce use of class static initialization blocks

     [ https://issues.apache.org/jira/browse/LOG4J2-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Sicker resolved LOG4J2-3459.
---------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

Added to master in [https://github.com/apache/logging-log4j2/commit/aab23d5c05bff2915c290dff3e73a0ae03caf43a]

> Reduce use of class static initialization blocks
> ------------------------------------------------
>
>                 Key: LOG4J2-3459
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3459
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: API, Core
>            Reporter: Matt Sicker
>            Assignee: Matt Sicker
>            Priority: Major
>             Fix For: 3.0.0
>
>
> There are numerous classes that use static initializer blocks to perform computation for caching some results. These should all generally be deferred until some other reference to the class such as instantiation of use of a singleton getter method.
> In general, this points to a lack of centralized initialization of the API. This should be addressed through a proper SPI.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)