When reconfiguring the JDK: localhost paavo # java-config-1 -L [sun-jdk-1.4.2.12] "Sun JDK 1.4.2.12" (/etc/env.d/java/20sun-jdk-1.4.2.12) [blackdown-jdk-1.4.2.03] "Blackdown JDK 1.4.2.03" (/etc/env.d/java/20blackdown-jdk-1.4.2.03) * localhost paavo # emerge jython Calculating dependencies... done! >>> Emerging (1 of 1) dev-java/jython-2.1-r6 to / * jython-2.1.tar.bz2 MD5 ;-) ... [ ok ] * jython-2.1.tar.bz2 RMD160 ;-) ... [ ok ] * jython-2.1.tar.bz2 SHA1 ;-) ... [ ok ] * jython-2.1.tar.bz2 SHA256 ;-) ... [ ok ] * jython-2.1.tar.bz2 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking jython-2.1.tar.bz2 ;-) ... [ ok ] * Using Generation-1 System VM: sun-jdk-1.4 After env-update && source /etc/profile JDK was changed. This is a bug beacuse the http://www.gentoo.org/doc/en/java.xml document states "Note: You no longer have to source the profile for updates to the user/system VM take place."
We should be able to update java-pkg.eclass to make calls to java-config, instead of relying on ${VMHANDLE} to be in the environment.
Created attachment 98335 [details, diff] teh patch like this
Applied a fix. Thanks for reporting.
