@ctrueden I was asking because I blew a Fiji installation with enabling the Java 8 update site (as mentioned before) without having a Java 8 installation on the machine (not having properly read the news post on the topic). I was wondering if we could have a check for an exisiting Java 8 installation before enabling the Java 8 update-site.
(although I guess you have thought about that and it is not quite as easy as I imagine..)
I want this all to be over with before the "next months" have passed.
By which I mean: soon, we should eliminate the Java-8 update site and reintegrate everything into the ImageJ and Fiji sites.
There is only one thing I want to do before we do that, really.
Create a launcher project in Java that requires the minimum possible version of Java, and performs any checks at startup to ensure the JVM is suitable. And if not, tell the user to upgrade, and then quit.
That way, we can have all JARs on the core update site built with Java 8, except for this one launcher project.