You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (Jira)" <ji...@apache.org> on 2023/08/22 14:03:00 UTC
[jira] [Commented] (GROOVY-5117) remove all references to java.util.logging from within groovy
[ https://issues.apache.org/jira/browse/GROOVY-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757486#comment-17757486 ]
Paul King commented on GROOVY-5117:
-----------------------------------
Actually Since Groovy 5 is JDK11 minimum, it might make sense for us to consider platform logging everywhere - and bridges exist there too. But that would be a different issue to this one.
> remove all references to java.util.logging from within groovy
> -------------------------------------------------------------
>
> Key: GROOVY-5117
> URL: https://issues.apache.org/jira/browse/GROOVY-5117
> Project: Groovy
> Issue Type: Improvement
> Environment: using groovy as script engine embedded within another application/framework
> Reporter: ron
> Assignee: Jochen Theodorou
> Priority: Major
>
> java does not allow multiple configurations of logging.
> java logging is initialized on class load.
> some applications (for example jboss 7) assume that they are the only ones to initialize the logging and will crash if java logging has already been initialized.
> solution: add and use groovy logging class, which, depending on system property configuration, may or may not use java.util.logging.
> remove all references to java.util.logging from all groovy classes (for example, org.codehaus.groovy.runtime.*)
> -- Ron
> http://sourceforge.net/projects/yajsw/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)