From: hiljusti <hiljusti@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dbeaver: version of the JVM is not suitable for this product
Date: Sat, 15 Jan 2022 06:34:59 +0100 [thread overview]
Message-ID: <20220115053459.dnAPC6nL8FAUIHCfeBQ05-zftPxAptvrUf1UW2RnyNM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34857@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
New comment by hiljusti on void-packages repository
https://github.com/void-linux/void-packages/issues/34857#issuecomment-1013617010
Comment:
Took me a while to find some steps to reproduce it, but tl;dr this would do it:
```
sudo xbps-install dbeaver
sudo xbps-install openjdk8
sudo xbps-alternatives --set openjdk8
dbeaver # fails with the error message
```
Maybe there are other ways to get to this state.
A quick fix is to do:
```
sudo xbps-alternatives --set openjdk11
```
But... I think there are reasons someone might want JDK 8 as a default, and still be able to use this app I guess. It's still an LTS version of Java, and some software still requires it for one reason or another. (Usually to run java bytecode compiled with some version <= JDK 7 that isn't supported by JDK 11)
next prev parent reply other threads:[~2022-01-15 5:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 22:34 [ISSUE] " jchook
2022-01-09 20:45 ` leahneukirchen
2022-01-09 20:46 ` leahneukirchen
2022-01-09 23:22 ` jchook
2022-01-09 23:57 ` jchook
2022-01-09 23:58 ` jchook
2022-01-15 5:34 ` hiljusti [this message]
2022-04-12 5:44 ` classabbyamp
2022-04-12 17:41 ` [ISSUE] [CLOSED] " leahneukirchen
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=20220115053459.dnAPC6nL8FAUIHCfeBQ05-zftPxAptvrUf1UW2RnyNM@z \
--to=hiljusti@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).