A DESCRIPTION OF THE REQUEST :
The current Info.plist /Library/Java/JavaVirtualMachines/jdk<???>/Contents/ only specifies the CommandLine capability for this runtime. This prevents the JRE from being used for any other application unless they actively work around this restriction.
The capabilities Apple provides for JRE6 are as follows:
JNI, BundledApp, WebStart, Applets, CommandLine
JUSTIFICATION :
Adding the capabilities originally specified by Apple for the JRE6 will enable JRE7 to used by any other application natively and prevent the user from having to additionally install legacy software that should not be used unless actually necessary.
The JRE6 Dialog that appears cannot be skipped unless JRE6 is installed and thus prevent the application from starting even if Java (JRE7) is available.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Installing JRE7 should suffice to run any modern application requiring Java on OS X without modifications to the capabilities or by omission of capabilities force a user to install JRE6.
ACTUAL -
The current JRE7 releases only specify the bare minimum of capabilities and either force the user to modify the capabilities, symlink JRE7 to the expected location of JRE6 (most common workaround), or simply install JRE6 as suggested by OS X.
CUSTOMER SUBMITTED WORKAROUND :
Temporary measures are manually editing of the Info.plist file stored in /Library/Java/JavaVirtualMachines/jdk<???>/Contents/ or by symlinking the JRE7 to the expected JRE6 location as described in various threads on stackoverflow.
The current Info.plist /Library/Java/JavaVirtualMachines/jdk<???>/Contents/ only specifies the CommandLine capability for this runtime. This prevents the JRE from being used for any other application unless they actively work around this restriction.
The capabilities Apple provides for JRE6 are as follows:
JNI, BundledApp, WebStart, Applets, CommandLine
JUSTIFICATION :
Adding the capabilities originally specified by Apple for the JRE6 will enable JRE7 to used by any other application natively and prevent the user from having to additionally install legacy software that should not be used unless actually necessary.
The JRE6 Dialog that appears cannot be skipped unless JRE6 is installed and thus prevent the application from starting even if Java (JRE7) is available.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Installing JRE7 should suffice to run any modern application requiring Java on OS X without modifications to the capabilities or by omission of capabilities force a user to install JRE6.
ACTUAL -
The current JRE7 releases only specify the bare minimum of capabilities and either force the user to modify the capabilities, symlink JRE7 to the expected location of JRE6 (most common workaround), or simply install JRE6 as suggested by OS X.
CUSTOMER SUBMITTED WORKAROUND :
Temporary measures are manually editing of the Info.plist file stored in /Library/Java/JavaVirtualMachines/jdk<???>/Contents/ or by symlinking the JRE7 to the expected JRE6 location as described in various threads on stackoverflow.
- relates to
-
JDK-8064542 JNI_CreateJavaVM can't be used in JRE on mac os x
-
- Closed
-
-
JDK-8066665 Call to JNI_CreateJavaVM requires installation of Java SE 6
-
- Closed
-