[
https://issues.apache.org/jira/browse/COLLECTIONS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986615#comment-13986615
]
Daniel Feist commented on COLLECTIONS-519:
------------------------------------------
> we should look at fixing the rest of Commons rather than re-instating the bad
> practise in Collections 3.
Can't disagree with that.
Agree on downside, not sure how it provides more flexibly though? It does
eliminate risks due to accidental hiding etc. in subclass as you described
though.
> private constructors in utility classes break existing code
> -----------------------------------------------------------
>
> Key: COLLECTIONS-519
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-519
> Project: Commons Collections
> Issue Type: Bug
> Affects Versions: 4.x
> Reporter: Radoslav Paskalev
> Fix For: 4.1
>
>
> Hello,
> In collections version 4.x all utility classes (example ListUtils, MapUtils,
> PredicateUtils....) have private constructors. I consider this to be a
> serious bug, as it breaks any possibility the classes to be extended by the
> users. The javadoc says that constructors are private in order to prevent
> class instantiation but this object instantiation is not really problem and i
> think it is more important to allow classes to be extended. The possibility
> to extend utility classes was one of the major selling points of commons.lang
> and commons.collections projects. In the latest commons.lang project the
> utility classes still have public constructors.
> Best Regards
--
This message was sent by Atlassian JIRA
(v6.2#6252)
