JDK-8150680 : JarFile.Release enum needs reconsideration with respect to it's values
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util.jar
  • Affected Version: 9
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2016-02-25
  • Updated: 2017-05-17
  • Resolved: 2016-07-14
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 b128Fixed
Related Reports
Relates :  
JDK-8132734 - JDK 9 runtime changes to java.util.jar to support multi-release jar files
Description
These issues with JarFile.Release came up in CCC and need to be addressed

1. Replace Release.RUNTIME object with Release.runtime() method

2. Perhaps also replace RELEASE.BASE with Release.base() method.  Consider exposing RELEASE.VERSION_8 even though 8 is not a "legal" version number for a multi-release jar.  

3. Reorder the Release enum values so new VERSION_XX values can be added to the end rather than inserted in the middle.  This keeps the ordinal values in the right sequence.
Comments
verified on jdk9-b156
15-02-2017
The concept of JarFile.Release may also need reconsideration in the light of the new Runtime.Version class. For example is JarFile.Release required? What if there are constants Version instances for every major release version?
26-02-2016