Perhaps a more general approach would be to unload com. Java-Updater.plist" , and remove the plist from /Library/Launch Agents?
Following the steps listed will enable you to avoid unforeseen version compatibility issues.
The last publicly available release of Java 6 is to be released on February 19th 2013.
After that date all new security updates, patches, and fixes for both the runtime and SDK of Java SE 6 will only be available through My Oracle Support, and will therefore only be available to users with a commercial license with Oracle.
Oracle will then start auto-updating all Windows 32-bit users from JRE 6 to JRE 7 with the update release of Java, Java SE 7 Update 11 (Java SE 7u11), due in February 2013. Oracle has decided that, in order to fix extensively-reported security problems, they will not only update Java 7 (their latest version of Java), they will also completely delete a completely separate product. They can be installed side-by-side, and many users have both Java 6 and Java 7 installed on their machines. Worse, it appears that they are taking it upon themselves to replace installations of Java 6 with Java 7 even if the users have only Java 6 on their machines.
Some of their applications depend on Java 6, and others might depend on Java 7, and these dependencies are typically hard-coded or configured to point to the correct, and different, file locations. As a result, he says, "You should strongly consider turning off automatic Java updates". "I actually think the best thing that the user could do is update their browser plug-in to the latest Java 7," he told us, "or simply disable Java in the browser." He also had a number of suggestions for how Oracle could deal with the current situation a.