Commit: r2520: Handle trunks with the process-exit option
Version 2520 was committed by wanmil on Thu, 07 Mar 2013 Handle trunks with the process-exit option
Hmm, there is no download for the new versions of mkgmap and the splitter? :? -- View this message in context: http://gis.19327.n5.nabble.com/Commit-r2520-Handle-trunks-with-the-process-e... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Uli, yes, splitter r295 required Java 1.7 without intention.This is fixed again with r296. mkgmap r2520 compiles fine on 1.6, but the unit tests fail because of the message regarding the switch to 1.7 Gerd
Date: Thu, 7 Mar 2013 18:24:08 -0800 From: ulibaer@gmail.com To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Commit: r2520: Handle trunks with the process-exit option
Hmm, there is no download for the new versions of mkgmap and the splitter? :?
-- View this message in context: http://gis.19327.n5.nabble.com/Commit-r2520-Handle-trunks-with-the-process-e... 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
GerdP wrote
Hi Uli,
yes, splitter r295 required Java 1.7 without intention.This is fixed again with r296. mkgmap r2520 compiles fine on 1.6, but the unit tests fail because of the message regarding the switch to 1.7
Gerd
Hi Gerd, thank you for the information! Then i think it's best, to already install Java 1.7. I have still Java 1.6 going strong... ;) Regards, Uli -- View this message in context: http://gis.19327.n5.nabble.com/Commit-r2520-Handle-trunks-with-the-process-e... Sent from the Mkgmap Development mailing list archive at Nabble.com.
but the unit tests fail because of the message regarding the switch to 1.7
?? Is there a unit test that checks for output on System.err? I should rerun the tests. We could also printout the message on System.out but I tried to make a very prominent warning ... WanMil
but the unit tests fail because of the message regarding the switch to 1.7
?? Is there a unit test that checks for output on System.err? I should rerun the tests. We could also printout the message on System.out but I tried to make a very prominent warning ...
WanMil
Using now System.out for the warning. The ArgsTest should work now. WanMil
participants (4)
-
Gerd Petermann -
svn commit -
UliBaer -
WanMil