unofficial mirror of bug-guix@gnu.org 
 help / color / Atom feed
From: Michael Rohleder <mike@rohleder.de>
To: Christopher Howard <christopher.howard@qlfiles.net>
Cc: christopher@librehacker.com, 42423@debbugs.gnu.org
Subject: bug#42423: icedtea: JAVA_HOME
Date: Fri, 31 Jul 2020 13:49:44 +0200
Message-ID: <873657ewfb.fsf@rohleder.de> (raw)
In-Reply-To: <f89d538f045bc4ad46d441a47b0d2636534edd75.camel@qlfiles.net> (Christopher Howard's message of "Sat, 18 Jul 2020 21:09:52 -0800")

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

Hi Christopher,

Christopher Howard <christopher.howard@qlfiles.net> writes:
> Hi, I'm not going to pretend to be a Java expert, but I was trying to
> build and run a Java application, and had to set JAVA_HOME manually. It
> is my understanding from my research[1] that applications often will
> want JAVA_HOME set to the path to the java install directory. It would
> seem like it would be useful if Guix set that as well for the icedtea
> and icedtea:jdk package.
>
> If there are good reasons for that not to be, perhaps more
> knowledgeable individuals will explain it.
>
> One part I'm not quite sure about is what JAVA_HOME would be set to if
> both icedtea and icedtea:jdk were installed.

I dont think this is a good idea (or even possible?):

From a Developer POV I think its pretty common to have many jdk's installed
(8,11,14 sometimes even 7). To what should JAVA_HOME be set/defaults in this
case?

I dont know a distribution which sets JAVA_HOME (per default) and I
think its much better to let the user or sysadmin decide which one is
best...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-19  5:09 Christopher Howard
2020-07-19 10:29 ` Julien Lepiller
2020-07-31 11:49 ` Michael Rohleder [this message]
2020-07-31 14:14   ` Christopher Howard
2020-07-31 15:10     ` Ricardo Wurmus

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=873657ewfb.fsf@rohleder.de \
    --to=mike@rohleder.de \
    --cc=42423@debbugs.gnu.org \
    --cc=christopher.howard@qlfiles.net \
    --cc=christopher@librehacker.com \
    /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

unofficial mirror of bug-guix@gnu.org 

Archives are clonable:
	git clone --mirror https://yhetil.org/guix-bugs/0 guix-bugs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 guix-bugs guix-bugs/ https://yhetil.org/guix-bugs \
		bug-guix@gnu.org
	public-inbox-index guix-bugs

Example config snippet for mirrors

Newsgroups are available over NNTP:
	nntp://news.yhetil.org/yhetil.gnu.guix.bugs
	nntp://news.gmane.io/gmane.comp.gnu.guix.bugs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git