Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Won't Fix
-
3.2
-
None
-
None
-
None
Description
I don't see any good reason why this CollectionUtils (and others) isn't final with a private constructor. There are no non-static methods, and any extension of them is going to have to call through to the super to avoid compiler warnings.
e.g. MyCollectionUtils.select() will provoke the warning that "static methods should be called directly" (on CollectionUtils).
Which would mean
MyCollectionUtils{
public static Collection select(){
return CollectionUtils.select();
}
Which really defeats the purpose. In Java5, we have static imports now - these provide more benefit than previous extension did anyhow.
Attachments
Issue Links
- breaks
-
COLLECTIONS-519 private constructors in utility classes break existing code
- Closed