unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Zachary Kanfer <zkanfer@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: After installing Java, what should I set JAVA_HOME to?
Date: Tue, 08 Nov 2016 16:13:00 +0100	[thread overview]
Message-ID: <87eg2m80oz.fsf@elephly.net> (raw)
In-Reply-To: <CAFXT+RMha_Q=xyxJYxHVkZExwhb+O0A-Lhi+uhwF5E9_=_x85Q@mail.gmail.com>


Zachary Kanfer <zkanfer@gmail.com> writes:

> But I started the gradle quickstart guide
> <https://docs.gradle.org/current/userguide/tutorial_java_projects.html>,
> and I've started running into problems. Right now I have $JAVA_HOME set to
> /home/zck/.guix-profile/, but I am suspecting that is not right. When I run
> `./gradlew clean`, I get the following error:
>
>     zck@zck-laptop:~/code/gradle-test$ ./gradlew clean
>     Downloading https://services.gradle.org/distributions/gradle-3.0-bin.zip
>
>     Exception in thread "main" javax.net.ssl.SSLException:
> java.lang.RuntimeException: Unexpected error:
> java.security.InvalidAlgorithmParameterException:
> the trustAnchors parameter must be non-empty

[…]

> [1] The manifest file to install javac is:
>
> (use-package-modules java)
>
> (packages->manifest
>  (list ;;java
>        icedtea
>        (list icedtea "jdk")))

You only need “(list icedtea "jdk")” here.  The “jdk” output of the
“icedtea” package includes the JRE, which is the only thing you get with
the standard output of “icedtea”.

Versions 6 and 7 of “icedtea” come with a build phase to generate a
keystore.  I’m using this successfully with “jgit”, which has to
validate SSL certs.

As to the value of JAVA_HOME: I only ever set it in Guix package
expressions, where it is set to the directory name of the store item for
the “jdk” output.

~~ Ricardo

  parent reply	other threads:[~2016-11-08 15:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02  4:38 After installing Java, what should I set JAVA_HOME to? Zachary Kanfer
2016-11-02  6:18 ` Chris Marusich
2016-11-08  4:20   ` Zachary Kanfer
2016-11-08 12:31     ` Ludovic Courtès
2016-11-08 15:15     ` Ricardo Wurmus
2016-11-09  7:01     ` Chris Marusich
2016-11-09 21:22       ` Hartmut Goebel
2016-11-28  5:15       ` Zachary Kanfer
2016-11-28  8:45         ` Ricardo Wurmus
2016-11-30 22:01           ` zloster
2016-12-01  8:59             ` Ricardo Wurmus
2016-11-28  9:59         ` Ludovic Courtès
2016-11-28 17:08         ` Hartmut Goebel
2016-11-29  2:34         ` Chris Marusich
2016-11-08 15:13 ` Ricardo Wurmus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-12 18:48 Radoslav Petrov
2016-12-01  2:18 ` Chris Marusich
2016-12-01 13:06   ` Ludovic Courtès
2016-12-01 13:07   ` 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=87eg2m80oz.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=zkanfer@gmail.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
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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).