Note that the JRE installs to /Library/Internet Plug-Ins/JavaAppletPlugin.plugin only, so it cannot easily be used by Java desktop applications and appears to be for applets only.
It also installs a System Preferences plugin that opens up a custom Swing-based settings panel that looks awful on a Retina MBP. It tries to replicate the look of the standard Apple Java Preferences app, but is confusing because it doesn't affect the system Java that you'd see when doing 'which java' from the command line.
The installer script then sets the permissions on /Library/Internet Plug-Ins/JavaAppletPlugin.plugin to root:wheel. This is the same as the bundled Java installations.
This does seem weird to me, as you said the java executable by default gets installed to /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java. Whereas the java executable within the jdk package gets installed to /Library/Java/JavaVirtualMachines/jdk1.7.0_06.jdk/Contents/Home/bin/java.
The images compressed a little on upload, so it actually looks even worse than in the image. The contrast between the sharp text everywhere else and the fuzzy Swing window is jarring.
For those who want to know, here is what is inside the .pkg files within the DMG. If you want to have a custom install directory in a non OSX specific directory structure then you can extract the packages and it should work appropriately.
I'm not sure what is the news here, I've been using OS X for five months and one of the first things I did was to get JDK from Oracle. I understand that Apple has stopped distributing it and Oracle will be the standard source to get JRE and JDK but I don't get how it was unavailable before this press release. Am I missing something? Otherwise title is misleading.
So speaking just in terms of the JRE, is there any reason to download it from Oracle instead of Apple? A separate Oracle updating program is a much less elegant solution than the current Software Updates integration that Apple uses.
Apple's already removed their own JRE from default OS X installs, demand-loading it only with explicit user authorization.
Furthermore they've sent out recent security updates partially disabling applet loading in web browsers and disabling the JVM entirely if it hasn't been used in a long while.
I think that the next step of completely shuttering Apple's JRE demand-loader will be a straight-up security win for most end-users, ensuring that only those who require Java have it.
Photoshop and other Adobe apps have components written in Java. Without Java, those components will silently fail. Thus, the on-demand Java installation hooks will be present for as long as current versions of CS are supported on OS X. For reference, Adobe CS 3, released 5 years ago, is still supported by Mountain Lion: http://www.adobe.com/products/creativesuite/faq.html#a139_12...
I suspect the on-demand Java installation process will be around for quite some time.
Here I am hoping for something like project jigsaw (or something else) to make it easy to modularize my applications and redistribute/install only the JRE pieces I need, and then I read "Starting with this release, JavaFX is now fully integrated into Oracle's Java SE implementation"
So much for a less bloated runtime. I confess I am not sure how big of a size impact JavaFX has (and I'm reasonably sure it has no runtime impact).
You may have an existing license-acceptance cookie depending on what else you might have done. Clear any oracle cookies and try again. You'll run into a fail page.
(I've worked on scripting JDK installs so have had to go around this by coding the cookie into curl and wget calls)
Java 7 is faster in some cases. Also, some Java apps will require Java 7 — but obviously that doesn't apply to you if you aren't planning on using any new Java apps and those don't force an upgrade.
Earlier betas indicated 'works on Snow Leopard', though I'm not sure how they tested it, because it never installed. Later site pages just said 'tested on Lion' or something like that.
There was a google code site that offered built versions with installers that worked on Snow Leopard (supposedly) but I could never get those to install right either.
Am I destined to have to upgrade to Lion/ML just to get Java7. ???
It also installs a System Preferences plugin that opens up a custom Swing-based settings panel that looks awful on a Retina MBP. It tries to replicate the look of the standard Apple Java Preferences app, but is confusing because it doesn't affect the system Java that you'd see when doing 'which java' from the command line.
The installer script then sets the permissions on /Library/Internet Plug-Ins/JavaAppletPlugin.plugin to root:wheel. This is the same as the bundled Java installations.