See bug 683.
Dm: The equals and hashCode methods of URL are blocking (DMI_BLOCKING_METHODS_ON_URL)
The equals and hashCode method of URL perform domain name resolution, this can result in a big performance hit. See http://michaelscharf.blogspot.com/2006/11/javaneturlequals-and-hashcode-make.html for more information. Consider using java.net.URI instead.
.. we should not have this one :)
USELESS_STRING: Invocation of toString on an array (DMI_INVOKING_TOSTRING_ON_ARRAY)
The code invokes toString on an array, which will generate a fairly useless result such as [C@16f0472. Consider using Arrays.toString to convert the array into a readable String that gives the contents of the array. See Programming Puzzlers, chapter 3, puzzle 12.
I need to find a good way to process the findbugs output so I can put a
todo list here.
In the meantime, I've pushed out a patch to github changing all the occurences
where toString was being called on an array (all 6 of them).
I haven't given this a whole lot of thought, so feel free to ignore until I
look more closely, the are all in other toString() methods.
Harvey, do you plan to make a pull request with your findings?