1. emerged dev-java/sun-jdk-1.4.2.09 2. emerged dev-java/blackdown-jdk-1.4.2.02 3. switched to blackdown using "java-config -S ..." 4. updated dev-java/sun-jdk-1.4.2.10 5. unmerged dev-java/blackdown-jdk-1.4.2.02 resulted in the situation that the file /usr/lib/mozilla-firefox/plugins/libjavaplugin_oji.so was linked to /opt/sun-jdk-1.4.2.09/jre/plugin/i386/ns610-gcc32/libjavaplugin_oji.so which wasn't found after step 5 so that firefox complained about that.
Not directly related to mozilla but to java packages.
This problem is a bit difficult to fix with the current system. We are currently planning to migrate to a new system would handle this a bit better. With this new system, the current system/user vm ends up being encapsulated by a symlink. For example, /etc/java-config/system-vm would point to /opt/sun-jdk-1.4.2.09. So, you could easily change the system vm, but applications wouldn't be trying to use the vm that was used at build time.
We now have an eselect module for handling the nsplugin. You will need to upgrade to the new Java system: http://www.gentoo.org/proj/en/java/java-upgrade.xml then use: 'eselect java-nsplugin list' to list the plugins.
