Hello Matthias,
The update version (the 31 in this case) you can set using the configure
parameter --with-update-version=31. In JDK8u, the source does not know
the correct value for this version number, so the distributor who builds
it needs to know and set it correctly.
-Erik
On 2019-06-21 12:39, Matthias Apitz wrote:
Hello,
We have ported OpenJDK to our Solaris SPARC servers and have a small
issue now:
The (older) Oracle Java says about the version:
sisis@srap13dsr1:> jdk1.8.0_31/bin/java -version
java version "1.8.0_31"
Java(TM) SE Runtime Environment (build 1.8.0_31-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode)
Our compilation of OpenJDK says:
sisis@srap13dsr1:> openjdk8/bin/java -version
openjdk version "1.8.0-internal"
OpenJDK Runtime Environment (build 1.8.0-internal-sisis_2019_05_23_13_28-b00)
OpenJDK 64-Bit Server VM (build 25.71-b00, mixed mode)
So far so good. The problem is that our software packages which need
Java are checking during installation the version string of Java and this
a bit hardwired. This would mean updating our packages so that they
accept the new OpenJDK. Or is there any correct configuration way to let
OpenJDK's Java punch the old version string 'java version "1.8.0_31"' ?
Thanks
matthias
