Unmerging a jdk or jre does not remove the appropriate entry so that java-config believes they are still there even if they are not. Not sure if java-config should be smarter, or if they ebuilds for jre and jdk should remove this entry... either way, one should do it...
Hmm.. yes. This one can get tricky fast, really: 1) merge sun-jre-1.4.0 2) java-config --set-system-vm=sun-jre-1.4.0 3) unmerge sun-jre-1.4.0 At this point, we should remove sun-jre-1.4.0 from the list of available vms, that's understandable, but should we remove it as the default system VM ? Probably not, as we have a policy of never messing with the user's configuration setup unless explicitly told so. This, however, means that if the user unmerges the default system VM, or a VM any of his users have as their default, things will stop working.
Okay. I updated the java.eclass, so the Java packages that inherit that one will get the desired functionality. I'm slowly moving all JDKs and JREs to using the java eclass, but I want to do it stepwise, in case it results in severe breakage..
