Hi all, Building commons-lang locally made me notice HashSetvBitSetTest, which made me wonder why we need it as a unit test.
I'm guessing it was originally used to support a design decision about which data structure to use. But having done it, we now have a relatively slow test (on my machine - 0.582 seconds out of a total seconds it takes to mvn test ~ 2.1%), which prints to stdout, and doesn't test any functionality of the code provided in commons-lang. Wouldn't it make more sense to @Ignore this test and just run it when a new jvm/jdk is tested? or even remove it completely? -Allon
