
Hi, I did not see any complains regarding the switch to 1.7. Up to now I still compile and test with 1.6, is it ok to do the switch now? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/switch-to-java-1-7-tp5778082.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

under windows java 1.7 works without probs from the beginning (except in the beginning some additional messages on compiling) - so since long 1.7 is perfectly fine... On 19.09.2013 09:18, GerdP wrote:
Hi,
I did not see any complains regarding the switch to 1.7. Up to now I still compile and test with 1.6, is it ok to do the switch now?
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/switch-to-java-1-7-tp5778082.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Hi
I did not see any complains regarding the switch to 1.7. Up to now I still compile and test with 1.6, is it ok to do the switch now?
Yes, I think there has been more than enough warning time. Although it is funny that I only changed to using 1.7 to run mkgmap in the last week! The builds on the website have been built with 1.7 for some time, but with a target of 1.6, so that they still run on 1.6. I'll change the message to say that 1.7 is now required. ..Steve
participants (3)
-
Felix Hartmann
-
GerdP
-
Steve Ratcliffe