Version History of Java 7 Update 15
Auto-update and update through Java Control Panel of JRE 6 will replace JRE 6 with JRE 7
- Since JRE 6 has reached its End of Public Updates Oracle is taking steps to protect consumer desktops. We will not leave a version of Java installed for which we no longer provide security updates.
- In order to do so, when updating from JRE 6, the update mechanism will not only install the latest version of JRE 7 but will also remove the highest version of JRE 6 on the system. This change will happen when the system is updated via the auto-update mechanism or by checking for updates directly from the Java Control Panel.
- Users who need to keep a version of JRE 6 in their systems can do so by manually installing the latest version of JRE 7 rather than relying on auto-update or updates through the Java Control Panel.
- If JRE 6 has already been removed from a system, but the user would like to restore it, earlier versions of Java can be accessed from the Java Archive.
- Note that Oracle strongly recommends leaving only up-to-date versions of the JRE on desktops. Retaining an older version of the JRE in your systems should only be done by expert users or enterprise administrators with a need for those earlier versions and an understanding of the associated risks.
Classic (Plug-in 1) Java Plug-in not supported
- When a user deselects the Next-generation plug-in(from JDK 6u10) option that is displayed in the Java Control Panel(JCP), an older(classic) plug-in will be chosen automatically. This classic Plug-in (also referred to as Plug-in 1) is not supported in the latest releases of JDK 7.
- The classic Plug-in is not supported or tested
- The classic Plug-in is not secure
- The classic Plug-in does not respect the security levels defined in the new JCP security slider
- The classic Plug-in is deprecated and will not be available in future Java SE platform releases.
- For more information, see Java Control Panel documentation.
- This release contains fixes for security vulnerabilities. For more information, see Oracle Java SE Critical Patch Update Advisory.