wrong classpath is set in designer-qtjambi

I suggest to not to define this variable because it should be already set to the correct value at system level.

The java-common package *should* probably handle setting the correct java environment (like JAVADIR). However, it does not at this point (as far as I can ascertain).

At this point, openjdk-6-jdk is a dep of this package, and JAVADIR is correctly set in most places to this dep. This was missed in the recent updates. So, the most correct fix at this time is to set JAVADIR to /usr/lib/jvm/java-6-openjdk.

Removing icedtea ref in designer-qtjambi and replacing with openjdk to match rest of qtjambi packaging.

Fixed in version 4.4.3-0ubuntu2.

And as an added bonus, there's going to be a 4.4.3-0ubuntu3 with additional fixes as the one correction above does not completely fix everything. :)

I still do not understand why there is an explicit reference to any JVM.
IMHO (any starting script for any Java application) should extract the correct Java runtime settings (classpath, jvm etc.) from the settings of update-java-alternatives and just maybe name one only as a fall-back option.

That is exactly the reason why update-java-alternatives exists: so people can select which JVM to use. With the current settings you will just see people hunting hopeless for bugs not knowing that qtjambi not uses their own JVM. (Please note that the shipped openjvm is still not the open-source fork of Sun's, so many people need to install a different JVM to get Java properly working.)

As I said in my previous note, java-common should probably do that (or some other package. not 100% sure which). Anyway, it doesn't.

Personally, I do not see any JAVADIR/JAVA_HOME in the environment and without it the script does not work. The java-alternatives do not set this in any way (that I can see).

So, until the java environment is setup to export a proper JAVADIR/JAVA_HOME from alternatives, this allows the package to work as expected.

Perhaps a seperate bug regarding the java environment might help?

Actualy, just re-read your last comment... let me look into the alternatives again.

Should have been marked released long ago.