> Grabbing a JDK 5 today requires quite some extra jumps in the downloads,
very true, and it has become even harder since Oracle's purchase of Sun > and we formally support building only against Java 5, by this > meaning Java 6 builds might actually fail (sometime a unit test I built GeoTools trunk recently (for the OSGi project we are trying to set up with Jody) on a OpenJdk 6 b16 on CentOS 5.5 x86_64 and it went very smoothly. > 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. Another field with a lot of problems (as always since 1.4) is all the XML / web services libraries included in the JRE. Behavior or included libraries versions can significantly change between Java 5 and 6. But all this is still what I would call "comfort" issues (not the same as having generics or not when you from 1.4 to 1.5, if you see what I mean). I'm fully aware that it is easier for me to say so since I don't have to maintain such a huge and complex codebase as GeoTools... ------------------------------------------------------------------------------ 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
