-
Bug
-
Resolution: Won't Fix
-
P3
-
7
-
x86
-
os_x
There is an application that uses the Info.plist definition for Java
applications and the javastubfile that can be used to wrap a Java
application and make it look native.
The attached java.1.6.app will start and quit immediately when run
with Java 1.6. With Java 1.7 however did get the error you can see
in the screenshot: "No compatible version of Java 1.6+ available".
AFAIK this should work to maintain upwards compatibility of the
"JVMVersion" flag in the Info.plist file.
This problem would occur with every application because
the 1.6+ seems not match the 1.7.
The setup for the application at
http://download.inetsoftware.de/clear-reports-free-latest.dmg
The application start fine if starts with Java on command line directly,
but you would see the error when double click to start the application
The problem is that the OSX launcher (.app directory) can not find the
Java VM with the needed version. It looks like that the Java VM is not
registered correctly in the OS. It is not a problem of the Java VM self.
It is a problem of the Java setup.
applications and the javastubfile that can be used to wrap a Java
application and make it look native.
The attached java.1.6.app will start and quit immediately when run
with Java 1.6. With Java 1.7 however did get the error you can see
in the screenshot: "No compatible version of Java 1.6+ available".
AFAIK this should work to maintain upwards compatibility of the
"JVMVersion" flag in the Info.plist file.
This problem would occur with every application because
the 1.6+ seems not match the 1.7.
The setup for the application at
http://download.inetsoftware.de/clear-reports-free-latest.dmg
The application start fine if starts with Java on command line directly,
but you would see the error when double click to start the application
The problem is that the OSX launcher (.app directory) can not find the
Java VM with the needed version. It looks like that the Java VM is not
registered correctly in the OS. It is not a problem of the Java VM self.
It is a problem of the Java setup.