From: Chris Marusich <cmmarusich@gmail.com>
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, 01 Nov 2016 23:18:30 -0700 [thread overview]
Message-ID: <87r36u5rrd.fsf@gmail.com> (raw)
In-Reply-To: <CAFXT+RMha_Q=xyxJYxHVkZExwhb+O0A-Lhi+uhwF5E9_=_x85Q@mail.gmail.com> (Zachary Kanfer's message of "Wed, 2 Nov 2016 00:38:36 -0400")
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
Hi Zachary,
Zachary Kanfer <zkanfer@gmail.com> writes:
> But I started the gradle quickstart guide, 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
>
> (further stacktrace elided)
Perhaps Java cannot find/access the truststore (or can access it but
found nothing in it)? Do you know what trust store is being used?
Where is it, and what are its permissions?
> Further supporting my suspicion that JAVA_HOME shouldn't be the guix
> profile is that I would think either guix or java should manage the
> directory, but not both.
I think a bigger question here is why do you need to use Gradle directly
to build your project? What's stopping you from using Guix to do it?
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-11-02 6:18 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 [this message]
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
-- 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=87r36u5rrd.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--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).