[Bug 1603692] [NEW] java-update-alternatives doesn't recognize jdkhl label

[Paul Smith]

Public bug reported:

java-common                  0.56ubuntu2
openjdk-8-jre-headless:amd64 8u91-b14-0ubuntu4~16.04.1

Newer versions of openjdk-8-jre-headless provide a .jinfo file that uses
a new tag "jdkhl" (for JDK headless).  Since update-java-alternatives
doesn't know anything about that tag, it ignores all those entries and
leaves them set to Java 7.

I spend about 45 massively frustrating minutes trying to figure out what
was going on before I realized that my javac was actually still Java 7
not Java 8 :(.

In addition to recognizing the new tag, I think that java-update-
alternatives should be modified to at least generate warning messages
for any tags that it doesn't recognize rather than failing silently and
leaving one believing that one's Java version has been changed
appropriately when it hasn't.

** Affects: java-common
     Importance: Unknown
         Status: Unknown

** Affects: java-common (Ubuntu)
     Importance: Undecided
         Status: New

** Bug watch added: Debian Bug tracker #825987
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825987

** Also affects: java-common via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825987
   Importance: Unknown
       Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to java-common in Ubuntu.
https://bugs.launchpad.net/bugs/1603692

Title:
  java-update-alternatives doesn't recognize jdkhl label

Status in java-common:
  Unknown
Status in java-common package in Ubuntu:
  New

Bug description:
  java-common                  0.56ubuntu2
  openjdk-8-jre-headless:amd64 8u91-b14-0ubuntu4~16.04.1

  Newer versions of openjdk-8-jre-headless provide a .jinfo file that
  uses a new tag "jdkhl" (for JDK headless).  Since update-java-
  alternatives doesn't know anything about that tag, it ignores all
  those entries and leaves them set to Java 7.

  I spend about 45 massively frustrating minutes trying to figure out
  what was going on before I realized that my javac was actually still
  Java 7 not Java 8 :(.

  In addition to recognizing the new tag, I think that java-update-
  alternatives should be modified to at least generate warning messages
  for any tags that it doesn't recognize rather than failing silently
  and leaving one believing that one's Java version has been changed
  appropriately when it hasn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/java-common/+bug/1603692/+subscriptions