-
Notifications
You must be signed in to change notification settings - Fork 168
Oracle JRE 9 not recognized #43
Comments
Oh screw you, Oracle! 😡 Thanks @dtuma David for reporting this. I will take a look and change the version comparison logic asap. |
The current JRE 9-ea build identifies as:
And the current JDK 9-ea build:
and it registers as:
Requesting a specific java version:
So compatibility with old Java/JDK versions must be achieved by requesting Oh man, Oracle opened the next gate to hell... Really don't want to know how many apps this change is going to break... |
Hi @dtuma, took a bit longer than expected, sorry... If you want to set a Java Version Requirement in the Plist file, please note that you have to use the following schema (noted in regex syntax):
If you're having trouble or if you think something is broken with the Java 9 support with my latest changes, please report back here... Note: I added extensive tests in This is an example output:
|
Please note that I'm on vacation until June 26 |
Hi @dtuma, have you been able to test the latest version from the |
I apologize for the slow reply. (I was out of the office as well, and thus away from the Mac where I could perform a test.) The version on the develop branch is working well with Java 9. Thank you so much for your responsiveness on this item! |
Great, thanks for testing this! Will release a new version soon... |
Released version 2.1.0 just now! |
Java 9 is scheduled for release in July 2017. It includes JEP 223, which changes the version numbering scheme of the Java platform: http://openjdk.java.net/jeps/223
The version extraction and comparison logic in universalJavaApplicationStub is not working against the new version numbers. As a result, a user with Java 9 installed may receive an error stating that no suitable Java version was found.
The text was updated successfully, but these errors were encountered: