build number

[Artem Ananiev]

Hi, Henri,

build number is a tag assigned by JDK release team when the build is 
released. MacOSX port is not merged with the main JDK workspace yet, so 
we don't have any promoted builds, so there are no build numbers.

Consider the following scenario. Somebody clones the forest and runs "hg 
update -r jdk7-b132" to update the workspace to the state that 
corresponds to JDK7-b132 and then changes a single line in some class or 
native code. Is it still b132? Even if no files are touched, the build 
may and most likely will not be the same as JDK7-b132 promoted build as 
the build environment is different.

Thanks,

Artem

On 4/6/2011 10:04 AM, Henri Gomez wrote:
> Hi to all,
>
> OpenJDK from bsd-port (and also the one from macosport) reports like this :
>
> openjdk version "1.7.0-internal"
> OpenJDK Runtime Environment (build 1.7.0-internal-henri_2011_04_04_12_18-b00)
> OpenJDK 64-Bit Server VM (build 21.0-b03, mixed mode)
>
> Latest build from OpenJDK (b136 for Linux for example), report the
> correct build number :
>
> java version "1.7.0-ea"
> Java(TM) SE Runtime Environment (build 1.7.0-ea-b136)
> Java HotSpot(TM) 64-Bit Server VM (build 21.0-b06, mixed mode)
>
> Did there is something to be adjusted in build to get this information
> so users could know the correct build number ?
>
> Thanks