Archive

Archive for the ‘Java’ Category

Automating Oracle Java 8 JDK updates

July 29, 2016 Leave a comment

To go along with a previous post about automating Oracle Java 8 updates, I’ve now posted a script to download and install the latest Java 8 Java Development Kit (JDK) from Oracle. Oracle has been releasing two separate versions of Java 8 simultaneously, so this script is designed to allow the user to set which version they want to install: the CPU release or the PSU release.
The difference between CPU and PSU releases is as follows:

  • Critical Patch Update (CPU): contains both fixes to security vulnerabilities and critical bug fixes.
  • Patch Set Update (PSU): contains all the fixes in the corresponding CPU, plus additional fixes to non-critical problems.

For more details on the differences between CPU and PSU updates, please see the link below:

http://www.oracle.com/technetwork/java/javase/cpu-psu-explained-2331472.html

For more information, see below the jump.

Read more…

Categories: Java, Mac OS X, macOS, Scripting

Java 8 Update 65 Redux – The Good, the Bad and the Failings

November 13, 2015 Leave a comment

With the release of Java 8 Update 65, Oracle has returned to using an application to install Java. This switch away from using installer packages is a problem for Mac admins who need to deploy Oracle’s Java 8 in their own environment. However, after doing some research, it looks like it is still possible to deploy Oracle’s Java 8 Update 65 using a standard installer package. For more details, see below the jump.

Read more…

Oracle’s Java 8 Update 66

October 21, 2015 4 comments

Following closely on the heels of Oracle’s release of Java 8 Update 65, Oracle has released Java 8 Update 66. This update is also using Oracle’s install application.

Screen Shot 2015 10 21 at 8 57 05 AM

What’s the difference between Update 65 and Update 66? Update 65 is a Critical Patch Update (CPU), which contains both fixes to security vulnerabilities and critical bug fixes. Update 66 is a Patch Set Update (PSU), which means it contains all the fixes in the corresponding CPU, plus additional fixes to non-critical problems. For more details on the differences between CPU and PSU updates, please see the link below:

http://www.oracle.com/technetwork/java/javase/cpu-psu-explained-2331472.html

So the short version is that Update 65 has “critical bug fixes” and Update 66 has “Update 65’s bug fixes, plus more bug fixes.”

You can get Oracle’s Java 8 Update 66 from the link below:

http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html

For more details on Java 8 Update 66, see below the jump.

Read more…

Oracle’s Java 8 Update 65 – The return of the Java install application

October 20, 2015 5 comments

For the past couple of releases, Oracle has used a standard installer package to install Java 8. With the release of Java 8 Update 65 though, Oracle returned to using an application to install Java.

Screen Shot 2015 10 20 at 3 40 39 PM

This switch away from using installer packages is a problem for Mac admins who need to deploy Oracle’s Java 8 in their own environment. However, after doing some research, it looks like it is still possible to deploy Oracle’s Java 8 Update 65 using a standard installer package. For more details, see below the jump.

Read more…

Modifying Oracle’s Java SDK to run Java applications on OS X

August 8, 2015 2 comments

As part of releasing the developer betas for OS X 10.11, Apple announced that El Capitan would be the end of the line for the Java 6 runtime and tools provided by Apple, with the clear statement that developers should be moving on to Oracle’s Java tools.

To completely replace Apple’s Java 6 tools, Oracle’s Java JDK (Java SE Development Kit) will need to be installed. This is because the Oracle Java JRE (Java Runtime Environment) on OS X is a browser plug-in for running Java via a web browser and does not include capabilities for running Java desktop apps or command line tools.

By default though, the Oracle JDK does not set several options to advertise the capabilities provided by the JDK to Java apps, which may cause applications that need those capabilities to fail to launch. The capabilities are actually present in the JDK, but those options need to be set before applications will recognize them as available.

To fix this, we need to add the following options to Oracle’s Java JDK:

  • BundledApp
  • JNI

 In turn, enabling these options means they need to be added to the list of JVMCapabilities stored in the following plist file:

/Library/Java/JavaVirtualMachines/jdk_version_info_goes_here.jdk/Contents/Info.plist

Screen Shot 2015 08 08 at 7 39 19 AM

For more details, see below the jump.

Read more…

Oracle’s Java 8 Update 40 has been updated again to …. Java 8 Update 40

March 16, 2015 9 comments

Oracle has released a new update for Java 8, but has continued their recent trend of not bumping the version number. Oracle has put out a new build of Java 8 but didn’t bump the version number from Java 8 Update 40, which makes this the third release of Java 8 Update 40.

At this point, it appears that Oracle is now providing the install application across the board. When you update an existing Java installation on OS X via Oracle’s Java update mechanism, you will receive Oracle’s install application for Java along with the selected option to install the Ask.com browser add-ons. If you download an installer from Java.com, you will also receive this install application.

Screen Shot 2015-03-16 at 3.47.54 PM

Screen Shot 2015-03-13 at 4.03.52 PM

Screen Shot 2015-03-13 at 3.57.05 PM

While the Oracle install application is not a standard installer package, it appears that Oracle had stored an installer package for Java 8 within the install application at the following location:

/path/to/install.app/Contents/Resources/JavaAppletPlugin.pkg


Screen Shot 2015-03-16 at 3.48.18 PM

The JavaAppletPlugin installer package is digitally-signed and does not include the Ask.com browser add-ons.

Screen Shot 2015-03-16 at 3.48.27 PM

The difference between the three Java 8 Update 40 releases

Early March’s Java 8 Update 40 (released on March 4, 2015): Java 8 Update 40 build 25 (1.8.40.25)

Mid-March’s Java 8 Update 40 (released on March 13, 2015): Java 8 Update 40 build 26 (1.8.40.26)

Just-Past-Mid-March’s Java 8 Update 40 (released on March 16, 2015): Java 8 Update 40 build 27 (1.8.40.27)

If you have Java 8 Update 40 installed, you can find out which build you have by running the following command in Terminal:

defaults read /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin/Contents/Info.plist CFBundleVersion

If you have Java 8 Update 40 build 25, the following string will be returned:

1.8.40.25

Screen Shot 2015-03-13 at 3.47.40 PM

If you have Java 8 Update 40 build 26, the following string will be returned:

1.8.40.26

Screen Shot 2015-03-13 at 4.06.45 PM

If you have Java 8 Update 40 build 27, the following string will be returned:

1.8.40.27

Screen Shot 2015-03-16 at 3.51.16 PM

For more details, see below the jump.

Read more…

Oracle’s Java 8 Update 40 has been updated to …. Java 8 Update 40

March 13, 2015 1 comment

Oracle has released a new update for Java 8, but this update has an interesting wrinkle. Oracle has put out a new build of Java 8, but didn’t bump the version number from Java 8 Update 40. So folks who have the previous version of Java 8 Update 40 installed may receive a message to update to Java 8 Update 40 from their current version, which will also be Java 8 Update 40.

For those thinking this sounds familiar, Oracle did the same thing with Java 8 Update 31 in February.

java_8_update_40

The difference between the two Java 8 Update 40 releases

Early March’s Java 8 Update 40 (released on March 3, 2015): Java 8 Update 40 build 25 (1.8.40.25)

Mid-March’s Java 8 Update 40 (released on March 12, 2015): Java 8 Update 40 build 26 (1.8.40.26)

If you have Java 8 Update 40 installed, you can find out which build you have by running the following command in Terminal:

defaults read /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin/Contents/Info.plist CFBundleVersion

If you have Java 8 Update 40 build 25, the following string will be returned:

1.8.40.25

Screen Shot 2015-03-13 at 3.47.40 PM

If you have Java 8 Update 40 build 26, the following string will be returned:

1.8.40.26

Screen Shot 2015-03-13 at 4.06.45 PM

Following installation of Java 8 Update 40 build 26, I tested on a 10.10.2 Mac against the following sites:

Oracle’s Java Test page: https://www.java.com/en/download/help/testvm.xml

Screen Shot 2015-03-13 at 4.10.06 PM

Java Tester’s Java Version page: http://javatester.org/version.html

Screen Shot 2015-03-13 at 4.09.53 PM

In both cases, the Java applets on those sites launched and worked without issue using Java 8 Update 40 build 26 (though the javatester.org applet needed to be whitelisted.)

To make things even more confusing, Oracle is providing a different installer for its update feed than it’s providing at the Java.com download site. When you update an existing Java installation on OS X via Oracle’s Java update mechanism, you will receive Oracle’s install application for Java along with the selected option to install the Ask.com browser add-ons.

Screen Shot 2015-03-13 at 4.05.41 PM

Screen Shot 2015-03-13 at 4.03.52 PM

Screen Shot 2015-03-13 at 3.57.05 PM

If you download an installer from Java.com, you will receive a standard digitally-signed installer package which does not include the Ask.com browser add-ons.

Screen Shot 2015-03-13 at 3.56.36 PM

Screen Shot 2015-03-12 at 7.10.42 AM

Unfortunately, Oracle has not provided any information about why these differences in installation methods exist. To make sure you’re installing Java 8 Update 40 without the Ask.com browser add-ons, I would currently recommend downloading the installer package available via the Java.com download site.

Follow

Get every new post delivered to your Inbox.

Join 313 other followers

%d bloggers like this: