Posted on 10-15-2014 09:57 AM
Anyone seeing how to globally kill the Java 8 Updater?
Oracle appears to have moved the setting/key to everyone's home drives at:
~/Library/Preferences/com.oracle.javadeployment.plist
Formerly in Java 7 the key was controlled by:
/Library/Preferences/com.oracle.java.Java-Updater JavaAutoUpdateEnabled -bool false
This version's updater is particularly useless, and can't even detect that Java 8 Update 25 is already installed. It proceeds to pop up anyway…
Posted on 10-15-2014 10:26 AM
I haven't dealt with it but just a thought: if you put that same plist file in /Library/Preferences, does it supersede the user preference?
Posted on 10-15-2014 10:48 AM
Thanks bpavlov-
com.oracle.javadeployment.plist doesn't start out being in /Library/Preferences by default so I'm not sure whether the Java 8 plugin is coded to check there for this key at all.
Posted on 10-15-2014 11:30 AM
The general model that many applications follow, or are supposed to follow anyway, is to first look for global preferences in /Library/Preferences/ and if not found there, next check the user space at ~/Library/Preferences/ So its possible deploying the configured plist there could work.
I'm saying this, but I have zero insight into what that plist contains. so if it references items in the user's directory, it may not work at all. Its worth a shot though.
Posted on 10-15-2014 05:24 PM
Personally, I think 8 u25 has two "updater" bugs.
1) If the software is up-to-date, it prompts to update.
2) If updates are disabled via the GUI, it successfully saves this setting at ~/Library/Preferences/com.oracle.javadeployment.plist. However, each time that Java preferences are opened, it deletes this plist file and starts anew.
Posted on 10-15-2014 06:11 PM
I noticed that the version supplied on the Java website was 1.8.25 (or something, I've since removed it for other reasons), but the auto update downloads 1.8.26. There was actually a difference in versions.
Posted on 10-15-2014 06:21 PM
Here's a possible workaround, though not well tested. Unknown if both referenced files are essential for this trick.
I leave it for others to test the viability of this option. I do not know what long-term repercussions will occur as a result of deploying locked files.
Even after deploying this, the Java preferences GUI will incorrectly display a checkmark indicating that it auto-checks for updates.
Posted on 10-16-2014 07:26 AM
Thanks for the advice and tips…
Anyone seeing whether there is a single key controlling this in Java 8 the way there was in Java 7?:
/Library/Preferences/com.oracle.java.Java-Updater JavaAutoUpdateEnabled -bool false