alexeid
commented
10 years ago I don’t think we should worry about this. Users that can’t install Java 7 shouldn’t be let loose on Bayesian MCMC software. I think we can assume that if we provide a link to Java 7 under the pre-requisites on beast2.org we should be fine.
Cheers Alexei
On 14/04/2014, at 10:50 am, rbouckaert notifications@github.com wrote:
Java 7 has some methods to more conveniently access Files and deal with class paths, and generic code can be made a bit cleaner, etc... Also, Java 8 is already on the horizon, so packages tend to be written against higher versions than 1.6.
However, for users that do not have a Java 7 JRE installed, it may be a nuisance to upgrade.
Can BEAST be configured so to assist users to upgrade -- e.g. by showing a dialog with relevant links and/or buttons to install the Java 7 JRE? For this, it needs to detect that the JRE is version 1.6, but since it is Java code, it should start on the Java 6 JRE. This could be done in a shell script, but this means maintaining it for the three OSs we support. So, it would be nice to do this in Java, but then that part of the code needs to be compiled against 1.6 in order to even start on a Java 6 installation -- so the build.xml file needs to differentiate between the two versions.
— Reply to this email directly or view it on GitHub.
Java 7 has some methods to more conveniently access Files and deal with class paths, and generic code can be made a bit cleaner, etc... Also, Java 8 is already on the horizon, so packages tend to be written against higher versions than 1.6.
However, for users that do not have a Java 7 JRE installed, it may be a nuisance to upgrade.
Can BEAST be configured so to assist users to upgrade -- e.g. by showing a dialog with relevant links and/or buttons to install the Java 7 JRE? For this, it needs to detect that the JRE is version 1.6, but since it is Java code, it should start on the Java 6 JRE. This could be done in a shell script, but this means maintaining it for the three OSs we support. So, it would be nice to do this in Java, but then that part of the code needs to be compiled against 1.6 in order to even start on a Java 6 installation -- so the build.xml file needs to differentiate between the two versions.