java9: -version output seems wrong: "9-Ubuntu"

Bug #1722410 reported by Andreas Hasenack
This bug affects 3 people
Affects Status Importance Assigned to Milestone
openjdk-9 (Ubuntu)
Fix Released

Bug Description

Unless something big changed upstream, or regarding a policy somewhere, the version string that's printed when you run "java -version" seems wrong with openjdk-9:

$ java -version
openjdk version "9-Ubuntu"
OpenJDK Runtime Environment (build 9-Ubuntu+0-9b181-4)
OpenJDK 64-Bit Server VM (build 9-Ubuntu+0-9b181-4, mixed mode)

That is causing at least one application I have, from the Brazilian IRS, to fail when parsing that string (screenshot attached):
For input string: "9-U"

It works just fine with jre 1.8, where the -version output is saner:
$ /usr/lib/jvm/java-8-openjdk-amd64/bin/java -version
openjdk version "1.8.0_144"
OpenJDK Runtime Environment (build 1.8.0_144-8u144-b01-2-b01)
OpenJDK 64-Bit Server VM (build 25.144-b01, mixed mode)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: openjdk-9-jre 9~b181-4
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 9 18:30:46 2017
InstallationDate: Installed on 2017-09-24 (14 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
SourcePackage: openjdk-9
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Andreas Hasenack (ahasenack) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in openjdk-9 (Ubuntu):
status: New → Confirmed
Revision history for this message
John Neffenger (jgneff) wrote :

For details on the new version strings, please see this JDK Enhancement Proposal that was included in OpenJDK 9:

JEP 223: New Version-String Scheme

Revision history for this message
Matthias Klose (doko) wrote :

the spec doesn't talk how to identify vendor builds, and doesn't talk about how to configure the build to include this information in the version information. Yes, it should be changed. Let's wait for the first "update" version, how the version information will change with that.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package openjdk-9 - 9.0.1+11-1

openjdk-9 (9.0.1+11-1) unstable; urgency=medium

  * OpenJDK 9.0.1+11 release.
  * Bump standards version.
  * Configure with an empty --with-version-pre setting. LP: #1722410.
  * Remove JamVM packaging bits. Closes: #877523.
  * Remove Shark packaging bits.
  * Fix java/javac/jar lockups on SMP Alpha (Michael Cree). Closes: #875288.
  * Fix crashes in i386 applications using JNI due to Hotspot workaround for
    Exec Shield (Ben Hutchings). Closes: #876069.
  * Re-enable building altzero architectures: Closes: #874292.
  * Update the zero-sparc patch (Adrian Glaubitz). Closes: #874265.
  * Fix recommendation of microhei/zenhei font packages. Closes: #868205.
  * Move jmod files into the openjdk-jdk-headless package. Closes: #878272.

 -- Matthias Klose <email address hidden> Fri, 27 Oct 2017 01:44:31 +0200

Changed in openjdk-9 (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.