[
https://issues.apache.org/jira/browse/GROOVY-12386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul King updated GROOVY-12386:
-------------------------------
Description:
Involves: two internal classes, Sys and Exceptions, create a System.Logger in a
static field. The spike switched them to java.util.logging. A gentler option is
a lazy holder so the logger is only created when something is actually logged,
which is an error path in both classes.
Impact on normal usage: with the JUL switch, users who installed a custom
System.LoggerFinder would see these two rare messages routed differently. With
the lazy option nothing changes on a JVM, so I would prefer that.
> groovy-json: keep System.Logger out of internal static initialisers
> -------------------------------------------------------------------
>
> Key: GROOVY-12386
> URL: https://issues.apache.org/jira/browse/GROOVY-12386
> Project: Groovy
> Issue Type: Improvement
> Reporter: Paul King
> Assignee: Paul King
> Priority: Major
>
> Involves: two internal classes, Sys and Exceptions, create a System.Logger in
> a static field. The spike switched them to java.util.logging. A gentler
> option is a lazy holder so the logger is only created when something is
> actually logged, which is an error path in both classes.
> Impact on normal usage: with the JUL switch, users who installed a custom
> System.LoggerFinder would see these two rare messages routed differently.
> With the lazy option nothing changes on a JVM, so I would prefer that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
