Charles L Hakes <[email protected]> writes: > 1.8.7 is starting up for me now. > > My “system” version was showing as old for a while and there was a > “fix” I found on-line that wasn’t holding after I quit terminal. > Tried many times to get it to work, but it would not until I tried to > demonstrate to one of the IT tech guys at school how it was not > working - then the update looked like it held. I still couldn’t run > 1.8.6 though.
Yeah, once I discovered what was going on, all of this became a lot more
clear. For those interested in the technical details, feel free to read
more here :-)
Mac OS X Java applications are started by the operating system running
the JavaApplicationStub shipped with the program in:
<application>.app/Contents/MacOS/JavaApplicationStub
The 'standard' version of this stub is responsible for finding a
suitable Java runtime environment and then calling it with the right
arguments to run the program. That's partially configured by the
application's MacOS description which is shipped with the program in:
<application>.app/Contents/Info.plist
The standard JavaApplicationStub looks at all of the Java runtimes
installed on the system in
/Library/Java/JavaVirtualMachines
Each of those also includes an 'Info.plist' file that describes the Java
runtime capabilities. In particular, in that file each JRE says what
kind of applications it supports under the JVMCapabilities
entry. Oracle's Info.plist includes only 'CommandLine' in this
set, so 'Bundled' applications (anything shipping as a desktop
application) will never match this JVM when using the standard
JavaApplicationStub.
So, we can fix this in two ways:
1) Adjust the Oracle JVM configuration to explicitly state that it can
run Bundled applications
2) Change the JavaApplicationStub to ignore this part of the JVM
Info.plist.
I tried method 1) and it worked great -- AltosUI came right up. However,
if you install a new Java, then that will overwrite any changes and
things will break again.
Then I found a replacement JavaApplicationStub which doesn't bother
looking at that JVM configuration value here:
https://github.com/tofi86/universalJavaApplicationStub
We're shipping a slightly modified version of this with AltOS which
makes all of our applications work with any installed JVM.
> Can the next step be getting the Bluetooth on the Mac recognizing the
> Teledongle? Still need a cable.
As neither Bdale nor I have a Mac OS X box for development, it's hard to
for us to do that, but it may happen at some point. Just finding a box
to test these Mac OS X install issues is a challenge.
--
-keith
signature.asc
Description: PGP signature
_______________________________________________ altusmetrum mailing list [email protected] http://lists.gag.com/mailman/listinfo/altusmetrum
