>
>> is stupidly dependent on hash iteration order, though other times
>> there are less obvious issues).
>
> Yes, we had this as well and ended up hacking the unit tests to check
> which version we are running. A bit ugly but I did not find any better
> solution.
>
I would recommend checking the size of the collection and doing a
containment test for each object.
e.g Checking a collection of 4 Strings would be something like
assertTrue(coll.size()==4);
assertTrue(coll.contains("first item");
assertTrue(coll.contains("second item");
assertTrue(coll.contains("third item");
assertTrue(coll.contains("fourth item");
Checking the version alone is not enough, you have to check for
vendor and platform too.
I know this because I have to use IBM sdk/ openjdk on different
platforms. Each of these sdks have their own collection
implementation producing the problems mentioned above.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
