Wrong version set in latest openjdk-8 builds

[Jan Henke]

The current openjdk-8 build has a wrong version number set. `java -version`, `javac -version` etc. report the version string of this OpenJDK build as "java 1.8.0_01-internal", which is clearly wrong. This also triggers warnings about unsupported version in third party applications.

Please update the build process, so that the reported version of openjdk-8 matches the actual version, like "1.8.0_72" or similar.

[Jan Henke (jhe)]

To clarify, this applies to the openjdk-8 build from xenial.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ben Butler-Cole (benbc)]

This is also still the case for the latest openjdk-8-jdk packages on Vivid and Wily. Is there any prospect of fixing this?

[Matthias Klose (doko)]

fixed for 16-04 LTS, no intent to fix for earlier releases

[Jan Henke (jhe)]

Sadly not really fixed yet. Up to date Xenial system with openjdk-8:

jan@XPS13 ~ $ java -version
openjdk version "1.8.0_03-Ubuntu"
OpenJDK Runtime Environment (build 1.8.0_03-Ubuntu-8u77-b03-3ubuntu3-b03)
OpenJDK 64-Bit Server VM (build 25.03-b03, mixed mode)

The OpenJDK version is reported as1.8.0_03, which is wrong. The correct Short version should be 1.8.0_77 (maybe with -Ubuntu). Please fix that, thanks!

[Launchpad Janitor (janitor)]

This bug was fixed in the package openjdk-8 - 8u91-b14-0ubuntu4

---------------
openjdk-8 (8u91-b14-0ubuntu4) xenial; urgency=medium

  * Update to 8u91-b14.
    - Addresses CVE-2016-0686 (S8129952), CVE-2016-0687 (S8132051),
      CVE-2016-3427 (S8144430), CVE-2016-0695 (S8138593),
      CVE-2016-3425 (S8143167), CVE-2016-3426 (S8143945).
  * Backport parts of 8132051 and 6926048 to fix the zero builds.
  * Add a versioned break to the oracle-java8-installer package. The
    package inflates the priority of the java alternatives again. See
    https://lists.ubuntu.com/archives/ubuntu-devel/2016-April/039324.html.

 -- Matthias Klose <email address hidden> Thu, 21 Apr 2016 16:25:37 +0200

[Greg Wilkins (gregw-wiltel)]

I am still seeing this bug after an update today.

Can the urgency be increased as this is breaking ALPN deployment for HTTP2 on Jetty servers and probably on several other servers that use the Jetty ALPN implementation (which is highly dependent on the JVM version!)

[Eloy Paris (peloy-chapus)]

This bug is fixed in 8u91-b14-2ubuntu1:

shell$ java -version
openjdk version "1.8.0_91"
OpenJDK Runtime Environment (build 1.8.0_91-8u91-b14-2ubuntu1-b14)
OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)

And based on the changelog, for Ubuntu 16.04, it should be fixed in 8u77-b03-3ubuntu4 and later. Commenter in comment #5 seems to have been running unfixed version 8u77-b03-3ubuntu3.

Do note that appending anything to the version update number (like "-Ubuntu"), as suggested in comment #5, is a bad idea -- some applications will crash with java.lang.NumberFormatException when parsing a string like "03-Ubuntu". Here's an example:

http://askubuntu.com/questions/762286/since-ubuntu-16-04-javaws-no-longer-run-app-while-previously-run-fine-on-ubuntu

The version update number seems to be assumed to be a number by several applications.

Fixed packages for Xenial should be produced as this breaks Java applications out there.

[Philip D'Ath (pid-9)]

I can confirm that poster #5 is correct - this was not been released into the main stream.

more /etc/os-release
...
VERSION="16.04 LTS (Xenial Xerus)"

sudo apt-get update
...
sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

java -version
Picked up _JAVA_OPTIONS: -Djava.net.preferIPv4Stack=true
openjdk version "1.8.0_03-Ubuntu"
OpenJDK Runtime Environment (build 1.8.0_03-Ubuntu-8u77-b03-3ubuntu3-b03)
OpenJDK 64-Bit Server VM (build 25.03-b03, mixed mode)