You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2013/10/16 10:21:43 UTC
[jira] [Closed] (LANG-842) Lack of consistency in comparaison api
[ https://issues.apache.org/jira/browse/LANG-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henri Yandell closed LANG-842.
------------------------------
Resolution: Won't Fix
Resolving per the above.
I've noted the inconsistency in a JDK 1.8 related issue for an overhaul of the date code: LANG-923
> Lack of consistency in comparaison api
> --------------------------------------
>
> Key: LANG-842
> URL: https://issues.apache.org/jira/browse/LANG-842
> Project: Commons Lang
> Issue Type: Improvement
> Components: lang.*, lang.time.*
> Affects Versions: 3.2
> Reporter: Pier-Luc Caron St-Pierre
> Priority: Trivial
>
> The comparaison api is lacking of consistency with null.
> Few instances :
> org.apache.commons.lang3.StringUtils#equals returns false if one of the parameter is null.
> org.apache.commons.lang3.ObjectUtils#equals returns false if one of the parameter is null.
> org.apache.commons.lang3.time.DateUtils#truncatedCompareTo throws IllegalArgumentException if one of the parameter is null
> org.apache.commons.lang3.time.DateUtils#isSameInstant throws IllegalArgumentException if one of the parameter is null
> I do not have any suggestion to fix that problem because any solution would break backward compatibility.
--
This message was sent by Atlassian JIRA
(v6.1#6144)