JDK-6590301 : HotSpot VM should have own version separate from JDK version
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 7
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,solaris_9
  • CPU: generic,sparc
  • Submitted: 2007-08-07
  • Updated: 2011-03-08
  • Resolved: 2011-03-08
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 6 JDK 7 Other
6u4Fixed 7Fixed hs10Fixed
Related Reports
Relates :  
JDK-6581408 - Most of serviceability tools fail in 6u3b01 due to version check
Description
HotSpot VM now has own release train: Hotspot Express.
Therefore it should have own version separated from JDK version:

<major version>.<minor version>-b<nn>

The first version will be "10.00-b15" which is currently 
"1.6.0_03-ea-b02" since we forked current VM after b14.

Current VM will be "11.00-b03" which is 1.7.0-ea-b17 now
or "11.00-b04" for b18.

The <minor version> will be used for already released VM which
needs a point fix for our big customers.
Comments
SUGGESTED FIX Webrev: http://prt-web.sfbay.sun.com/net/prt-archiver.sfbay/data/archived_workspaces/main/c2_baseline/2007/20070817134027.kvn.6590301/workspace/webrevs/webrev-2007.08.17/index.html HotSpot VM now has own release train: Hotspot Express. Therefore it should have own version separated from JDK version: <major version>.<minor version>-b<nn>[-<identifier>][-<debug_target>] where <identifier> is PRT/JPRT job ID or 'internal' or the value of HOTSPOT_BUILD_VERSION specified on command line, <debug_target> is 'debug', 'jvmg' or 'fastdebug'. The <minor version> will be used for already released VM which needs a point fix (special update) for our big customers. The version and build numbers are specified in make/hotspot_version file. Each time the sources are promoted to master workspace the value of HS_BUILD_NUMBER should be incremented. Each time workspace is forked into update/performance workspace values in current workspace should be updated: increment HS_MAJOR_VER and reset HS_BUILD_NUMBER to 01. The first version will be "10.00-b16" which is currently "1.6.0_03-ea-b03" since we forked current VM after b14. Current VM will be "11.00-b05" for b19. The -Xinternalversion output will include JRE version for which VM was built. It is defined by FULL_VERSION variable. By default FULL_VERSION is set to JDK_MAJOR_VER.JDK_MINOR_VER.JDK_MINOR_VER defined in make/hotspot_version file: RE build: Java HotSpot(TM) Server VM (10.00-b16-fastdebug) for solaris-sparc JRE (1.6.0_03-ea-fastdebug-b03), built on Aug XX 2007 21:26:57 by "java_re" with Workshop 5.8 PRT build: Java HotSpot(TM) Server VM (11.0-b05-20070816201531.kvn.6590301-jvmg) for solaris-sparc JRE (1.7.0), built on Aug 16 2007 21:26:57 by "PRT" with Workshop 5.8 VM version and build numbers are always present at the beginning of VM version string: PRT: 11.0-b05-20070816201531.kvn.6590301-jvmg JPRT: 11.0-b05-2007-08-17-032152.kvn.6590301-jvmg own: 11.0-b05-internal-jvmg RE: 11.0-b05-jvmg Serviceability Agent checks only VM major version. The supported VM version is defined by SA_VERSION variable. By default it set to HS_MAJOR_VER. The same jvm_version_info structure layout is used to pass version info to libraries with micro, update, special_update values are always 0. I also moved VM copyright values into make/hotspot_version.
20-08-2007
EVALUATION See description.
07-08-2007