MXJ on OSX only launches with a JDK installed , provide support to launch with JRE only installed on OSX

[pslack]

mxj for OSX relies on command /usr/libexec/java_home to acquire the home path for installed java, however this function only works to identify installed JDK's and doesn't recognize plain old JRE installs. #$!@

[cassiel]

Speaking from a position of relative ignorance here, but: given that "mxj quickie" can compile Java source, doesn't that suggest that mxj requires a JDK? (Personally I'd be happy for quickie to die and mxj to only require a JRE.)

[pslack]

@cassiel It's a good point Nick thanks for your feedback, I'm really looking at the runtime deployment scenario and an issue that comes up for WaveDNA end users on OSX. When they install the latest JRE, patches with MXJ will fail because currently MXJ can only detect JDK installations and cannot detect JRE installations. This is a lower priority annoyance factor to address, the JDK is 400 Mb download and the JRE is 70 Mb

[cassiel]

As I said, I'm personally fine with a JRE-only dependency, and for quickie to die. Of whatever mxj community is out there, I'd expect the active developers to have JDKs and entire toolchains (or to be like me and script stuff in Jython, Clojure, or even JS). Having said that, I should probably check that all the scripting systems do work JRE-only.

[kristofb]

Hello all, for runtime deployment, I adapted Peter's code so now, it's working fine. Max 8 properly detects JRE now. I created a merge request.