You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Thomas Neidhart (JIRA)" <ji...@apache.org> on 2013/03/05 22:30:13 UTC
[jira] [Resolved] (COLLECTIONS-446) Overload
CollectionUtils.isEqualCollection to accept an Equator instance
[ https://issues.apache.org/jira/browse/COLLECTIONS-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Neidhart resolved COLLECTIONS-446.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 4.0
Added in r1453012.
Thanks for the suggestion!
> Overload CollectionUtils.isEqualCollection to accept an Equator instance
> ------------------------------------------------------------------------
>
> Key: COLLECTIONS-446
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-446
> Project: Commons Collections
> Issue Type: Improvement
> Components: Collection
> Affects Versions: 4.0
> Reporter: Matt Lachman
> Priority: Minor
> Fix For: 4.0
>
> Attachments: COLLECTIONS-446.patch
>
>
> As of COLLECTIONS-242, a new Equator interface has been added to the API. It would be nice to take advantage of that when comparing collections so it can be done on something other than {{Object.equals(Object other)}}. I propose a new method signature as below:
> {code:java}
> public static boolean isEqualCollection(Collection a, Collection b, Equator e)
> {code}
> Related to this is my post on StackOverflow: [http://stackoverflow.com/questions/15094818/compare-two-java-collections-using-comparator-instead-of-equals]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira