"/usr/lib/jvm/default-java" not changed by "sudo update-alternatives --config java"
Bug #687263 reported by
Raffi Enficiaud
This bug affects 12 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
java-common (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: java-common
After a
sudo update-alternatives --config java
setting for instance the sun JVM as the default, the link
/usr/lib/
still points to "java-6-openjdk". However, in
/usr/lib/
the "default" is the first java in $__jvm_all, which is then used in
/usr/lib/
called by some programs (such as for instance Freemind).
I am running Maverick, java-common 0.38.
To post a comment you must log in.
Hi
What you see here is "intended behavior" (at least in case of the default-java symlink and update- alternatives) . The issue here is probably that what Java packagers understand with "default" from what users expect. "default-java" has been used by packagers to denote the default Java implementation used for compiling Java packages.
I can clearly see how you would come to the conclusion you did and I have taken this up with the Debian Java Team. Though any changes to how default-java behaves is out of the question for Maverick (too many packages depend on the behavior). Most likely we will introduce a new symlink for this purpose in Natty (or later).
As for java-wrappers and how it handles this case. I suspect the tool will need an update to properly handle this case; whether this can make it into Maverick is an entirely different case. Since I do not work on this tool I will not make any promises on this; however, you should be able to work around this issue by using JAVA_FLAVOR (see man 7 java-wrappers).
~Niels