The source/makefiles are not aware of the build number. It's assigned
from an external source at the time of building a promoted build. If you
want your version number to better match 8 GA, you will have to play
around with the configure arguments --with-build-number and possibly
--with-milestone.
Also, as David pointed out, in JDK 8, hotspot has it's own numbering.
/Erik
On 2014-12-03 06:13, David Holmes wrote:
On 3/12/2014 12:25 PM, Medi Montaseri wrote:
Hi,
Just wanted to confirm some issues:
I am interested in building the latest (tip) of jdk8 GA release.
1- jdk8 GA is different from jdk8u (u is for updates), I should get
the src from http://hg.openjdk.java.net/jdk8/jdk8
2- The latest tagged version of the src is
"jdk8-b132 9106:43cb25339b55"
3- I confirm that I have the latest src (for GA) by running "hg tags"
like
unix> cd srcDir/jdk ; hg tags | head -2
tip 9107:687fd7c7986d
jdk8-b132 9106:43cb25339b55
I go ahead and build everything and then run "java -version" and I see
openjdk version "1.8.0-20141202"
OpenJDK Runtime Environment (build 1.8.0-20141202-HDS-174701)
OpenJDK 64-Bit Server VM (build 25.0-b70, mixed mode)
Q- Why am I seeing "build 25.0-b70" ? Does this "b70" has anything to
do with above "jdk8-b132" ?
That is the hotspot version number and build number as used in the GA
build of JDK 8. It is correct.
java version "1.8.0"
Java(TM) SE Runtime Environment (build 1.8.0-b132)
Java HotSpot(TM) Server VM (build 25.0-b70, mixed mode)
David
-----
Thanks
Medi
