JDK-8214549 : Bump maximum recognized class file version to 58 for JDK 14
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 14
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-11-30
  • Updated: 2019-06-25
  • Resolved: 2019-06-13
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 14
14 b01Fixed
Related Reports
Relates :  
Description
Each JDK platform release define a class file format whose major version is one greater than the last.

For JDK 14, the maximum recognized class file version should be 58.
Comments
No actual change is needed in hotspot to bump the max version. The max comes from a define set by the build system based on the version-numbers file. All we do in hotspot is add a new #define for the current JDK version, but even that isn't essential as nothing uses it at the version change. We'd only need it if checking for something specific to the new classfile version.
06-06-2019

Review thread: http://mail.openjdk.java.net/pipermail/hotspot-dev/2019-June/038394.html
06-06-2019