the regression Test JNLPClassLoaderTest has two problems.
1.) it will occasionally fail (about 1/3 of the time form me on Windows box) with a BlackListException.
2.) it will write to the actual users deployment.properties file.

The first problem is caused by the two tests testMainJarBlackListed and testMainJarBlackListed_NoCache setting up a jar as blacklisted, that is used in other tests. We do not know order tests will be run, if these are run first, that jar is still blacklisted (and the config is not cleaned up) when another test using that jar is run.
This should be fixable by having test properly clean up for itself.

Second problem may apply to other tests as well - will check, but calling:
Config.setInstance(new ClientConfig()) will result in possibly of values being written to users deployment.properties file. Most other tests use:
           Config.setInstance(new ClientConfig() {
                public void storeConfig() {
                }
            });
to insure config entries modified durring the test are neverf written out.