I've successfully emerged sun-jdk-1.4.1_01. --list-available-vms lists it I've done a --set-system-vm to the new sdk which worked and reported success. Alas when I check the environnment (even after an env-update) JAVA_HOME and JAVAC and the other JAVA environment variables still point to the old jdk
what happens if you log out and then log back in, and could you send the result of: find /etc/env.d/java
the results of find /etc/env.d/java: /etc/env.d/java /etc/env.d/java/20sun-jdk-1.4.0 /etc/env.d/java/20sun-jdk-1.3.1.04 /etc/env.d/java/20sun-jdk-1.4.1.01 and I'm sorry. I didn't logout and in again. I just opened another shell. After having done that the environment is now set correctly. Joerg
Im CC'ing azarah and cretin since its a bug in sandbox. If im wrong please excuse me, but you both are working now on sandbox AFAIK. =)
How is it sandbox's fault ? Any change to /etc/env.d/ will be obvious to portage as it always run env-update, and source /etc/profile (or maybe it was /etc/profile.env). For already running shells, it is different however ... you need to either relogin or source /etc/profile ... This is not a bug, but how shells work ... you cannot set an environment variable in a subshell and expect it to be exported to the parent shell. If you ask me, this bug is invalid.
Closing this bug, since its invalid
