From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: intellij-idea-community-edition: use jetbrains jdk
Date: Tue, 04 Oct 2022 20:45:17 +0200 [thread overview]
Message-ID: <20221004184517._5VmalFJHaokb-2fBomOzWxxc06pFMmPtoSXLzv2Mlk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39683@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]
There's a merged pull request on the void-packages repository
intellij-idea-community-edition: use jetbrains jdk
https://github.com/void-linux/void-packages/pull/39683
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
Trying to run intellij with an openjdk will error on startup complaining about missing AWT modules which aren't in that distribution. Instead of depending on any java environment via the `java-environment` virtual package, depend explicitly on the jetbrains jdk and modify the desktop entry to launch intellij with that jdk.
With these changes, intellij is only launched with the jetbrains jdk by default when you use the desktop entry. You can still launch it using any java environment when using the executable directly by setting the `IDEA_JDK` variable on the command line.
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
next prev parent reply other threads:[~2022-10-04 18:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 23:27 [PR PATCH] " dexgs
2022-10-03 23:29 ` [PR PATCH] [Updated] " dexgs
2022-10-03 23:47 ` dexgs
2022-10-04 18:45 ` classabbyamp [this message]
2022-10-04 18:58 ` Chocimier
2022-10-04 19:00 ` dexgs
2022-10-04 19:03 ` classabbyamp
2022-10-04 19:04 ` dexgs
2022-10-04 19:10 ` classabbyamp
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=20221004184517._5VmalFJHaokb-2fBomOzWxxc06pFMmPtoSXLzv2Mlk@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).