Affects Version/s: 1.1.0
Fix Version/s: 1.1.1
LogFactoryImpl.java:1250 in the 1.1 release has this line:
// try the parent classloader
currentCL = currentCL.getParent();
which does seem to be a likely cause for the exception.
This code should be executed under an AccessController, so that granting the logging jar the appropriate permissions can fix the problem; without this, all calling code also needs to have that permission.
Maybe we should wrap method discoverLogImplementation in an AccessController, covering all cases like this?