Application is using Java 6 from Apple instead of Java 7 from Oracle on Mac OS X?

java macos bundle java-7

40,112

Solution 1

Issue

Your Mac OS X application bundle has been created with an app bundler which is not compatible with Oracle's Java 7 package. The bundler you were using could be, for example, Jar Bundler provide by Apple which only works for Apple's Java 6 System Packages.

Apple has given up support for Java as an integrated System Packages from Java 7 and later. As a consequence you have to go for the Oracle Java 7 Third Party package and their application package bundle solution. This allows you to create and deploy Oracle Java 7 based application bundles on Mac OS X 10.7.3 and onwards.

The underlying technical issue you are facing is Apple's native Objective-C based JavaAppLauncher binary and the format it uses in Info.plist is only working with Apple's Java 6 System Packages and the JavaAppLauncher Info.plist combination coming from Oracle is only working for Oracle's Java 7 Packages.

As you are using a JavaAppLauncher supporting Apple's Java 6 System Packages, it will always pick up the Apple Java 6 System Package installed on your Mac.

There is a video, where Scott Kovatch, the lead engineer for the Mac OS X port of the Java platform at Oracle is talking on DEVOXX about how app bundling for Oracle Java 7 is working in great detail.

Solution

To create app bundles based for Mac OS X 10.7.3 and onwards based on

and above, you have to use Oracle's app bundler

lib/appbundler-1.0.jar containing the Ant Task com.oracle.appbundler.AppBundlerTask

With Oracle's app bundler you have now the choice to run your packaged app with the default Oracle Java 7 Package installed on your Mac here:

/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/

or the Oracle Java 7 JRE you inline in your packaged application

MyJavaMacOSXApp.app/Contents/PlugIns/

Note: There are pros and cons for both approaches, but you need the last one with your own JRE if you want to go to the Apple App Store with your bundled app.

What needs to be done

Download appbundler-1.0.jar and move it to <project>/lib/appbundler-1.0.jar

Add the following to your <project>/build.xml

<property environment="env" />

<taskdef 
    name="bundleapp" 
    classname="com.oracle.appbundler.AppBundlerTask" 
    classpath="lib/appbundler-1.0.jar" />

<target name="bundle">
    <bundleapp 
        outputdirectory="dist" 
        name="MyJavaMacOSXApp" 
        displayname="My Java Mac OS X App" 
        identifier="com.example.MyJavaMacOSXApp" 
        shortversion="1.0"
        applicationCategory="public.app-category.developer-tools"
        mainclassname="com.example.MyJavaMacOSXApp">
        <runtime dir="${env.JAVA_HOME}" />
        <classpath file="dist/MyJavaMacOSXApp.jar" />
    </bundleapp>
</target>

Note: You need to replace MyJavaMacOSXApp with your application data. You can find here some additional AppBundlerTask options, as this example shows only how how it works in its simplest form.

After you run the bundle target with ant bundle you will find MyJavaMacOSXApp.app in the <project>/dist directory.

What does the `<runtime dir="${env.JAVA_HOME}" />` element?

Inlining Oracle Java 7 Package (JRE)

The Ant target above copies the Oracle Java 7 Package (JRE) from your

JAVA_HOME

into

MyJavaMacOSXApp.app/Contents/PlugIns

So the application package is totally self contained and does not need an Oracle Java 7 Package (JRE) installed on the target system at all. Like you can see in the following screen shot of such a deployed MyJavaMacOSXApp.app:

MyJavaMacOSXApp Inline JRE

Wiring default Oracle Java 7 Package (JRE)

If you want to use the default Oracle Java 7 Package (JRE) installed on the application bundle target Mac under

/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/

you have to remove the

<runtime dir="${env.JAVA_HOME}" />

element fromt the bundle task. Like you can see in the following screen shot of such a deployed MyJavaMacOSXApp.app:

MyJavaMacOSXApp Inline JRE

Source of MyJavaMacOSXApp.java

package com.example;

import java.awt.*;
import javax.swing.*;

public class MyJavaMacOSXApp extends JPanel {

    public MyJavaMacOSXApp() {
        JLabel versionLabel = new JLabel("java.version=" + System.getProperty("java.version"));
        JLabel homeLabel = new JLabel("java.home=" + System.getProperty("java.home"));
        setLayout(new BorderLayout());
        add(versionLabel, BorderLayout.PAGE_START);
        add(homeLabel, BorderLayout.PAGE_END);
    }

    private static void createAndShowGUI() {
        JFrame frame = new JFrame("MyJavaMacOSXApp");
        frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
        MyJavaMacOSXApp newContentPane = new MyJavaMacOSXApp();
        newContentPane.setOpaque(true); 
        frame.setContentPane(newContentPane);
        frame.pack();
        frame.setVisible(true);
    }

    public static void main(String[] args) {
        SwingUtilities.invokeLater(new Runnable() {
            public void run() {
                createAndShowGUI();
            }
        });
    }
}

What if my app has multiple jar files?

Just add as many <classpath file="dist/additional.jar" /> entries as you need.

Note: The order of elements in the bundle task isn't preserved at runtime of your bundled app. The java.class.path gets built up at runtime by the native JavaAppLauncher as it reads in the *.jars from MyJavaMacOSXApp.app/Contents/Java directory.

Just for completeness, this is how Info.plist looks like:

<?xml version="1.0" ?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
    <dict>
        <key>CFBundleDevelopmentRegion</key>
        <string>English</string>
        <key>CFBundleExecutable</key>
        <string>JavaAppLauncher</string>
        <key>CFBundleIconFile</key>
        <string>GenericApp.icns</string>
        <key>CFBundleIdentifier</key>
        <string>com.example.MyJavaMacOSXApp</string>
        <key>CFBundleDisplayName</key>
        <string>My Java Mac OS X App</string>
        <key>CFBundleInfoDictionaryVersion</key>
        <string>6.0</string>
        <key>CFBundleName</key>
        <string>MyJavaMacOSXApp</string>
        <key>CFBundlePackageType</key>
        <string>APPL</string>
        <key>CFBundleShortVersionString</key>
        <string>1.0</string>
        <key>CFBundleSignature</key>
        <string>????</string>
        <key>CFBundleVersion</key>
        <string>1</string>
        <key>NSHumanReadableCopyright</key>
        <string></string>
        <key>LSApplicationCategoryType</key>
        <string>public.app-category.developer-tools</string>
        <key>JVMRuntime</key>
        <string>jdk1.7.0_17.jdk</string>
        <key>JVMMainClassName</key>
        <string>com.example.MyJavaMacOSXApp</string>
        <key>JVMOptions</key>
        <array>
        </array>
        <key>JVMArguments</key>
        <array>
        </array>
    </dict>
</plist>

Important documents this answer is based on:

There is also a well maintained fork of appbundler itself, with many more features and bugfixes.

https://bitbucket.org/infinitekind/appbundler

Solution 2

Your system isn't really up to date. I am not saying this is causing your issue. But just to be on the safe side I would role forward to the latest and greatest.

Role your system forward via System update, that you are on Mac OS X 10.8.2
Install a fresh JRE 1.6.0_43 from Apple aka Java for OS X 2013-002
Install a fresh JDK 1.6.0_43 from Apple aka Java for OS X 2013-002 Developer Package Mar 4, 2013. In order to get the Apple JDK you have to login here with your Apple ID (free Developer Account) and search for the term "Java for OS X 2013-002 Developer Package". Unfortunate there is no direct link for that package.
Delete your outdated Oracle JDK: sudo rm -rf /Library/Java/JavaVirtualMachines/jdk1.7.0_12.jdk. Note: Thats safe because in the next step we are installing the current Oracle JDK 1.7.0_17.
Download and install Oracle JDK 1.7.0_17 for Mac OS X. Note: This does also include the JRE 1.7.0_17 from Oracle.
Do a reboot.

After you have finished all steps from above, please come up with the following output again:

Which OS X version do you use?
What dumps the command /usr/libexec/java_home -V out?
What dumps the command /usr/libexec/java_home out?
What dumps the command echo $JAVA_HOME out?
What dumps the command echo $JAVA_ARCH out?
What dumps the command /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -version out?
What dumps the command ls /Library/Java/JavaVirtualMachines out?
What dumps the command /System/Library/Frameworks/JavaVM.framework/Commands/java -version out?

Just document the steps and the effort you did in your original question. So it reflects your progress.

UPDATE: The solution is to create a Mac OS X application bundle with Oracles AppBundlerTask. For details see my other answer here: https://stackoverflow.com/a/15271448

Solution 3

The Java version required by the app is probable specified in the application's metadata. If you right-click on the app and select Show Package Contents and browse to the Info.plist file, you should find entries which define the JVM that the application will use. E.g.

    <key>JVMVersion</key>
    <string>1.5</string>

OSX may choose to use a lower JVM if the application requests it.

Solution 4

Try installing this:

http://support.apple.com/kb/dl1572

InteliJ works just fine, while I'm still on Java SE 7 using for example NetBeans.

java -version
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)

Solution 5

EDIT: Uwe's impressive answer is absolutely correct for the OP who it turns out was using the AppLauncher. My initial read of the question was that it related to command-line issues on OSX with Java 6 vs Java 7. The comments on the original question show I was wrong. However, anyone having command-line issues may find the below a simpler solution.

ORIGINAL: My circumstances seemed the same as I thought the OP had: Java 1.7 perfectly on the command-line but mvn failing and complaining about 1.6, general compilation had been working fine using sbt and IntelliJ. I only started having problems compiling a third-party project with mvn.

I found this to work well and be much simpler:

http://www.jayway.com/2013/03/08/configuring-maven-to-use-java-7-on-mac-os-x/

All I needed from that was the following in .profile:

export JAVA_HOME=`/usr/libexec/java_home -v 1.7`

Set that variable and mvn worked well.

View more solutions

40,112

Author by

amod

I am a software developer with strong desire to learn and work on new technologies and solve complex problems with my solid programming knowledge and analytical skills. Currently, I am a Software Developer at Honeywell, Atlanta. I did Master in Computer Science from Lamar University, USA. I had worked as a Senior R&D Engineer in Nokia Networks for 2+ years and before that, I was a software developer in Persistent Systems Ltd for 2 years. In Nokia Networks I was part of core R&D team which design and implement complex telecommunication related algorithms to optimize the mobile network. While working, along with honing my programming skills, I became adept at analytical thinking, debugging, troubleshooting and team working. My core responsibilities also contain guiding junior developer to complete the task provided to them. I like writing code to make day to day life easier. Apart from coding my hobby is to write Blogs I used to write Blogs on various technology available on internet, games, gadgets, social networking, software, Cloud-based applications. I like reading blogs as well, exploring software products and gadgets. I am also a founding member of website CampFestiva.com which publish college events happening all over India. I have been working hard on this for more than 3+ years to make it what it is now. Campfestiva is a non-profitable attempt to provide information about various opportunities to students in India.

Updated on March 15, 2020

Comments

amod about 4 years
I am testing my current application with Mac OS X which has Java 7 from Oracle installed. Instead using Java 7 from Oracle, it's using Java 6 from Apple. The default system output of java -version is showing 7.

I tried most of the things mentioned in different sites, but I was unable to fix this issue.

JAVA_HOME is also properly set.

I am using the Mac only for testing purposes. I really need some guidance on this.

When I run it with Eclipse by selecting JRE 7, it runs properly. Thus there is nothing wrong with the application. I am missing something on Mac OS X.

My Java system environment looks like this:
- OS X version
  
  10.8
- /usr/libexec/java_home -V
```
Matching Java Virtual Machines (3):
1.7.0_12, x86_64: "Java SE 7" /Library/Java/JavaVirtualMachines/jdk1.7.0_12.jdk   
1.6.0_37-b06-434, x86_64: "Java SE 6" /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
1.6.0_37-b06-434, i386: "Java SE 6" /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home

/Library/Java/JavaVirtualMachines/jdk1.7.0_12.jdk/Contents/Home
```
- /usr/libexec/java_home
```
/Library/Java/JavaVirtualMachines/jdk1.7.0_12.jdk/Contents/Home
```
- echo $JAVA_HOME
```
/Library/Java/JavaVirtualMachines/jdk1.7.0_12.jdk/Contents/Home/
```
- JAVA_ARCH is not set
- /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -version
```
java version "1.7.0_12-ea"
```
- ls /Library/Java/JavaVirtualMachines
```
jdk1.7.0_12.jdk
```
- /System/Library/Frameworks/JavaVM.framework/Commands/java -version
```
java version "1.6.0_37"
```
I guess my current JDK is pointing to something wrong.
amod about 11 years

Yes there was 1.4+ in the info.plist. After making it 1.7; its giving me an popup no compatible version of Java 1.7. However java -version command is properly working.
amod about 11 years

adding further. It is requesting to set Java Preferences but since I reinstalled java I am unable to get tht option (apple removed it). Please let me know if sumhing is possible
Jintian DENG about 11 years

@amod0017 According to developer.apple.com/library/mac/#documentation/Java/Referenc‌e/…, you may change it to 1.6+ and give it a try.
amod about 11 years

I made it 1.7 it didnt worked. Please check my previous comments.
amod about 11 years

I started the whole stuff and will get back to you.
Uwe Günther about 11 years

@amod0017 Have a look at my other answer here: stackoverflow.com/a/15271448/287984 It looks like this will solve your issue.
amod about 11 years

Using App Bundler will it create a single jar for the whole application. I have multiple jars in my project and I want them separated?
amod about 11 years

BDW I am really thankful to you for your continuous efforts on solving this problem :)
Uwe Günther about 11 years

@amod0017 I changed the answer post. You can find it under 'What if my app has multiple jar files?' Oracles AppBundler will preserve all your *.jars in the 'MyJavaMacOSXApp.app/Contents/Java' directory. I hope this answer was helpful for you and if you think this is the answer to your issue I would appreciate it if you flag this answer post as the answer to your question (green tick).
amod about 11 years

Just last few questions. I am using installanywhere for creating the .app file. Can you give some pointers to it please.
Uwe Günther about 11 years

@amod0017 With the standard way described here in this post and suggested by Oracle for doing application packages for Java 7 on Mac OS X 10.7.3+ you have now a *.app package. Just stick this application package in a standard Mac OS X disk image (aka *.dmg file) and ship it to the customer. Details can be found here: stackoverflow.com/questions/96882/…
amod about 11 years

here you go man for all your efforts you have the bounty before it expires... To be very honest this is not a perfect answer I was looking for. There are lots of things involved but I will be working on the things you told me and will be keeping you updated. But you truly deserves this bounty because you helped me a lot. Please give me your email id so that I can ask you something if required.
Uwe Günther about 11 years

@amod0017 I appreciate the bounty and the answer tick! Looks like your problems could fill a chapter in a book about Java development on Mac OS X. Nevertheless I think if you create an application package how it is described here - you are in good shape to to go on to build a dmg file for deployment to the end user. My email is public in my profile since day one. Just check if you can find it there if not let me know.
Uwe Günther about 11 years

@lance-roberts Thanks for your efforts fixing the typos in my post. I like reviews, especially if the go this way.
Uwe Günther about 11 years

@sixlettervariables Like I mentioned in my answer there are 2 different native JavaAppLaunchers, one from Apple aka Jar Bundler, which is working with Apples Java System Packages only. The latest one from Apple is 1.6.0_43, there will be no one for Java 7. And the other one is from Oracle, aka as the AppBundlerTask, which is working with Oracle Java System Packages only. The earliest Java version from Oracle really working with Mac OS X 10.7.3 and above was 1.7.0_04. I hope this removes any ambiguity and doubts.In addition to the 2 official one, there are some 3rd party approaches out.
Uwe Günther over 10 years

The original poster had an issue with using the Apple AppLauncher for Oracle Java within its own Application bundle. This has nothing to do with using the java command line stub for kicking of maven via mvn on the command line.
Mukesh Kumar Singh about 10 years

@UweGünther the .app bundle generated by this process does not take argument from command line. When i run this command open MyJavaMacOSXApp.app --args arg1 arg2 arg3 arg4 it opens application but argument does not goes to application's main function. why ??? is there any solution for this ?
Mukesh Kumar Singh about 10 years

@UweGünther take a look my question here, stackoverflow.com/questions/22218375/…, please answer this if you can.
Andrew E about 10 years

@UweGünther, you are, of course, correct. But for viewers reading only the OPs question (i.e. not the comments following it), as I did when landing on the question from a Google search, it's reasonable to conclude the issue is a command-line problem and not the larger issue you identified and solved. I want to save those readers the time of going down the application plist rabbit hole to no avail, as I did.
simmerman almost 10 years

This is a great very thorough answer. As an improvement I suggest pointing to a well maintained fork of Appbundler with many more options and bugfixes here bitbucket.org/infinitekind/appbundler
Jack over 9 years

@UweGünther thanks for your answer, how about Maven based projects?
ziggurism almost 9 years

Upon trying these steps in Mac OS X Yosemite, I get this error: BUILD FAILED NetBeansProjects/MyJavaMacOSXApp/build.xml:89: java.nio.file.NoSuchFileException: NetBeansProjects/MyJavaMacOSXApp/Info.plist Should there be an Info.plist file somewhere?
Ketan over 8 years

I have a 3rd party app that wont work in El Capitan after upgrading. This solution above makes it work in El Capitan now. I would rather have it working properly with the new Java version but this will do :)