public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Wiktor Wandachowicz" <siryes@gmail.com>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] JAVA_HOME set to 1.4.2
Date: Mon, 31 Jul 2006 18:55:21 +0200	[thread overview]
Message-ID: <254054bc0607310955m5e3128d0n794d387fb9a3c683@mail.gmail.com> (raw)
In-Reply-To: <44CE11E6.5000800@gentoo.org>

> That's actually not true. What you lose, is the benefit of not having
> the current VM tied to the environment. Specifically, if you don't have
> a user VM set... JAVA_HOME would point at the system VM... but if at
> some point, you set a user VM, JAVA_HOME would still point to the
> system VM until you source whichever file you add that snippet to.
>
> It is extremely important to note that if you decide to use the snippet
> for root, then java-config-1 has no way of knowing what the generation-1
> VM is, because it uses JAVA_HOME to determine this.

That's what I've meant when I wrote "some of the benefits".
Independence from the environment settings was the most obvious
one. But thanks for the clarification straight from the source.

Given the consequences, I think that the script snippet from the
docs can be put in a file. Then it could be sourced only when
necessary before running specific scripts. This way Kurt can have
best of both worlds, benefits from generation-2 and working
scripts that depend on JAVA_HOME variable.

Regards,
Wiktor

-- 
Registered Linux user #390131 (http://counter.li.org)
-- 
gentoo-java@gentoo.org mailing list



      reply	other threads:[~2006-07-31 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 13:08 [gentoo-java] JAVA_HOME set to 1.4.2 Kurt Guenther
2006-07-31 13:15 ` Wiktor Wandachowicz
2006-07-31 14:21   ` Joshua Nichols
2006-07-31 16:55     ` Wiktor Wandachowicz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=254054bc0607310955m5e3128d0n794d387fb9a3c683@mail.gmail.com \
    --to=siryes@gmail.com \
    --cc=gentoo-java@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox