From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 58591@debbugs.gnu.org
Subject: bug#58591: Java packages do not appear to keep a reference to their inputs
Date: Mon, 17 Oct 2022 22:45:54 -0400 [thread overview]
Message-ID: <87edv5yhlp.fsf@gmail.com> (raw)
In-Reply-To: <025A8B84-E6C6-43EC-AAF6-CC93DC2F2BAC@lepiller.eu> (Julien Lepiller's message of "Tue, 18 Oct 2022 00:03:27 +0200")
Hi Julien,
Julien Lepiller <julien@lepiller.eu> writes:
> You're right, java package don't retain references to there input,
> that's why we propagate required dependencies (mh… sometimes). I don't
> know how they could reference dependencies directly.
Could we, along with installing Java classes as directories instead of
.jar archive files [0] at a more specific prefix, define a search path
specification that'd set CLASSPATH? Currently I don't see anything
setting CLASSPATH outside of the build systems, so even if we propagate
Java things, I don't see how it'd find them in a profile.
[0] Not exactly sure how that's done yet, but it's mentioned here: https://docs.oracle.com/javase/8/docs/technotes/tools/windows/classpath.html
--
Thanks,
Maxim
next prev parent reply other threads:[~2022-10-18 2:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 21:04 bug#58591: Java packages do not appear to keep a reference to their inputs Maxim Cournoyer
2022-10-17 22:03 ` Julien Lepiller
2022-10-18 1:43 ` Mark H Weaver
2022-10-18 2:45 ` Maxim Cournoyer [this message]
2022-10-18 7:01 ` Maxime Devos
2022-10-18 7:36 ` Liliana Marie Prikler
2022-10-18 13:14 ` Maxim Cournoyer
2022-10-18 13:21 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-10-18 14:17 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-10-18 14:53 ` Maxim Cournoyer
2022-10-18 14:56 ` Maxim Cournoyer
2022-10-18 15:32 ` Julien Lepiller
2022-10-18 23:25 ` Maxim Cournoyer
2022-10-18 13:29 ` Maxim Cournoyer
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=87edv5yhlp.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=58591@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).