Comment 17 for bug 334186

Am I the only one here who finds it ironic that the status on this in Java is "New" when this problem has been around since at least Feisty? (That is, Feisty which came out two and a half years ago...)

As an uneducated layperson, it seems that you always have java where you have soprano, but you don't always have soprano where you have java, ergo this could be fixed by having an install script with soprano that found the latest version of java and linked to it. The java package could also have something that called that same script (if soprano is installed) to update the linkage for each new java version.

Now if only I knew how to code! ;)