RFR: 8144062: Determine appropriate module for jdk.Version

Alan Bateman Alan.Bateman at oracle.com
Thu Feb 25 08:06:43 UTC 2016

On 25/02/2016 05:59, Iris Clark wrote:
> Hi, Alan, Mandy, and Mark.
> After exploring a few module options (jdk.Version, jdk.dev [0]),
> it looks like the best choice is to move jdk.Version to
> java.lang.Runtime.Version (a nested class of Runtime).  It supports
> the values returned by the java.{vm.}?version and
> java.{vm.}?specification.version system properties.  By making
> Version an SE API, it may be exported by the java.base module.
> Please review the following changes to move jdk.Version to
> jdk.lang.Runtime.Version.  Note that beyond the package name and
> class declaration (to static), the only other changes in Version
> are related to indentation.
This looks good. We should probably change the synopsis on the JIRA 
issue to make it clearer that it is promoting Version to a standard API.

Once this is in then the multi-release JAR file patch can be updated to 
make use of this.


More information about the core-libs-dev mailing list