Sometimes a testing of random 3rd party jars is desirable to raise testing coverage. The actual code in such jars may not be executed (if we test JIT-compiler, Compile-the-World, or class loading, for example).

The problem is that such jars can still contain unwelcome or even malicious code in their clinit ("static { ... }" blocks), which get executed.

We could avoid the potential harm by WhiteBox-controllable removing the clinit methods during class loading. And still allow for the testing.