09.08.2010, 18:49
(09.08.2010, 10:09)routeconverter Wrote:That is exactly what I mean. To stay compliant with linux/unix/BSD (macosx) error checking it should be 1 instead of 10 in case of an incorrect version.(09.08.2010, 09:27)hvdwolf Wrote: What this application lacks is a test application that checks for the correct java version. I don't know how easy or difficult it is to write a simple jar to check for the java version. This version check jar checks the java version: If OK start the jar, If wrong version report it to the user and exit.
So you'd like to do something like this inside the script?
RESULT_CODE='java -jar VersionCheck.jar'
where the result code is 0 for OK and something like 10 if it failed (plus a dialog for the user). And it had to be compiled against Java 1.1 like the applet on the download page to be useful. I guess that's half an hour of effort plus some testing...
(09.08.2010, 10:09)routeconverter Wrote: And as a side note: the prereleases have a Java version check for a version greater than 1.6.0_13 since there is a bug inside the XML parser in previous versions. But that code is compiled against Java 6...I made the upgrade to Snow Leopard as well so I can't test anymore against lower than java 6. Same for Ubuntu 10.04, that only comes with java 6.x as well.
However, if the error code from the prerelease could be "catched" as well that would be just as handy. I don't know however how I should "catch" the error code from a java command, but I will do some googling.
