[rfc] [icedtea-web] blacklist for reproducers

[Jiri Vanek]

Hi!

This is second from total of 5 patches which are introducing Tets For Applets[1]

Thus particular one is introducing  blacklist. The test-engine is delivered to class-path together 
with all reproducers' testcases. If the file form engine is interface, have no @Test methods or does 
not meet constructor requirements, then the file fails, and this is making our statistics misleading.
Also I'm expecting growing of engine (now I'm planing @bug and @browser annotations and some more 
logic around. See content of ignore-list after all this changes[2]. Also I would like to refactor 
ServerAccess class little bit in long term (as it have grown littlebit and have to much inner 
classes right now) future...

Probably cleaner solution will be to separate testengine from testaces more then it is now, but I 
have tried this refactoring and I was getting deeper and deeper and it was bringing more and more 
issues. From this I'm really for blacklist rather then for refactoring.
Also one more benefit is here - you can easili blacklist all reproducers except one or two fro make ;)

Best regards J.

[1] http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2012-March/017799.html
[2] 
http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20120320/8ef6bdfe/browserTests-blacklist-0001.diff