[ https://issues.apache.org/jira/browse/GROOVY-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Theodorou resolved GROOVY-5117. -------------------------------------- Assignee: Jochen Theodorou Resolution: Won't Fix I am closing this issue for now, since JUL bridges exist. If [~rzorzorzo] sees things different I invite him to reopen the discussion here. > 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)