> Yes, unfortunately when it comes to java libs this is "widespread" to > say the least. >
Often this isn't even intentional. For example the failure in the static memory leak checker isn't caused by its codebase (no private class is referenced); the exception is thrown at runtime when test case fields are collected and there is an attempt to measure the size of leftover objects. If somebody leaves an instance of Timezone or Locale this leads to a runtime security exception. Dawid
