JDK-8145098 : JNI GetVersion should return JNI_VERSION_9
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 9,9-repo-jigsaw
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-12-10
  • Updated: 2017-05-17
  • Resolved: 2016-03-03
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b110Fixed
Related Reports
Relates :  
JDK-8079466 - JNI Specification Update and Clean-up (JDK 8)
Relates :  
JDK-4528386 - JNI version number should be incremented for 1.4
Sub Tasks
JDK-8174955 :  
Release Note: Update JNI Version Number - Closed
Description
We need to add JNI_VERSION_9 and change CurrentVersion to JNI_VERSION_9 so that it gets returned by JNI GetVersion.

There is a jni.h in the jdk repo too so that will need to be updated at the same time.
Comments
The JNI updates in jake require the JNI version to be rev'ed so I will restore the m3 label to this issue. The plan for this issue is that it will go in via hs-rt once the issue of whether it should be JNI_VERSION_9 or JNI_VERSION_9_0 is resolved and the CCC approved.
12-02-2016
Just to mention that we've updated the JVM TI version in the jake forest so that jvmti.h defined JVMTI_VERSION_9.
28-01-2016
or maybe JNI_VERSION_9, we'll need to check into that. Update: I've brought up the topic of the JNI version here: http://mail.openjdk.java.net/pipermail/verona-dev/2015-December/000324.html
05-01-2016
Should it be JNI_VERSION_9_0 ?
10-12-2015