Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
When using the "indy" setting, it tries to read a system property to enable logging.
This change enables a JVM Security Manager to block this setting and therefore simply ignore the setting to use the default: do not log.
From a security manager, you might otherwise catch a SecurityException containing:
access denied ("java.util.PropertyPermission" "groovy.indy.logging" "read")
Not only is this not recoverable, but the IndyInterface class will be inaccessible thereafter due to it being in a static block that fails (the dreaded NoClassDefFoundError).