Installation of the package breaks automatic version detection

[Daniel Cardin]

the ubuntu packages for java install to /usr/lib/jvm using a pattern like this :

java-6-sun (symlink)
java-6-sun-1.6.0.03

However, proper jvm detection is done using the pattern

jdkVERSION
jreVERSION

Second problem, the directory is named [...].0.03 where the convention seems to be to use an underscore.

so at the very least there should be a symlink jre1.6.0_03 to java-6-sun-1.6.0.03

This will make the following command work correctly :

$ java -version:1.6+ -version

java version "1.6.0_03"
Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
Java HotSpot(TM) Server VM (build 1.6.0_03-b05, mixed mode)

instead of:
Unable to locate JRE meeting specification "1.6+"

[Matthias Klose (doko)]

where is this naming convention used/followed?

[Daniel Cardin (daniel-cardin)]

I am trying to find information about this but it's very scarce. I think I will have to look at the actual source code for the launcher.

I can only tell you the actual "behavior" for now. If the directory has the right name, java picks it up.

[James Stansell (jamesstansell)]

"-version:1.6+" is documented by Sun somewhere - I haven't looked at it for a year or more now. Hmm - http://java.sun.com/javase/6/docs/technotes/tools/solaris/java.html has a little bit about it.

[Daniel Cardin (daniel-cardin)]

It documents the option's format, not the actual process of locating the jvm though.
that's what I'm looking for

[Daniel Cardin (daniel-cardin)]

bump. this is still the case with Jaunty

[Noah (noah-noah)]

I just ran into this problem with Ubuntu 9.04 2.6.28-15-generic.

[Benjamin Redling (benjamin-rampe-deactivatedaccount)]

It's the same with Lucid Lynx .

[rusivi2 (rusivi2-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported should be reproducible with the live environment of the Desktop CD development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.