Joshua Nichols - Latest comments on JAVA_HOME pointing to generation-1 system vm

In response to: JAVA_HOME pointing to generation-1 system vm

Mike Slinn [Visitor] — Wed, 29 Nov 2006 20:11:45 +0000

Here is an easy way to set JAVA_HOME to the system JVM:

export JAVA_HOME=`sudo java-config -O`

In response to: JAVA_HOME pointing to generation-1 system vm

Mark (noob) [Visitor] — Sat, 05 Aug 2006 10:14:42 +0000

Sorry, I was following this thread after i tried following the gentoo java upgrade guide and i didnt get any output when i type java-config-1 -L. I was refered to this page from gentoo forums. Thanks for the help anyway

In response to: JAVA_HOME pointing to generation-1 system vm

Joshua Nichols [Member] — Fri, 04 Aug 2006 21:36:36 +0000

If you have to ask, you may not want to be testing them, since they are pretty experimental (hence package.mask)... but they go in /etc/portage/package.unmask.

In response to: JAVA_HOME pointing to generation-1 system vm

Mark (noob) [Visitor] — Fri, 04 Aug 2006 21:32:46 +0000

so where do i add these new lines to my system?

# Joshua Nichols (02 Aug 2006)
# Testing new versions of java-config, which will let us remove
# JAVA_HOME from env, which points to generation-1 system vm
=dev-java/java-config-1.3.0-r3
=dev-java/java-config-2.0.26-r6

in etc/profile.d? exists on my system at the moment.

In response to: JAVA_HOME pointing to generation-1 system vm

Caster [Visitor] — Thu, 03 Aug 2006 15:29:42 +0000

...unless "&ltjava-config-2*" is added to java-config-2's RDEPEEND (damn HTML filtering :)

In response to: JAVA_HOME pointing to generation-1 system vm

Caster [Visitor] — Thu, 03 Aug 2006 15:28:19 +0000

Hmm emerge -uvaDN world pulls both versions because java-vm-2.eclass depends on both 1.3* and 2.0*.
Emerge -uav java-config pulls only 2.0 unless "

In response to: JAVA_HOME pointing to generation-1 system vm

Joshua Nichols [Member] — Thu, 03 Aug 2006 13:03:24 +0000

Perhaps java-config-2 could depend on java-config-1, or vice versa? Not sure if that would cause havor to the dependency tree though.

In response to: JAVA_HOME pointing to generation-1 system vm

Caster [Visitor] — Thu, 03 Aug 2006 12:42:27 +0000

There must be a way to enforce that both versions are updated at the same time. Currently due to portage slotting bug, only java-config-2 will be updated in world deep update, leaving java-config-1 version depending on JAVA_HOME which is borked by the profile.d. Not that it matters for building gen 1 packages, because java-pkg.eclass already sets JAVA_HOME according to VMHANDLE before using java-config-1...