-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot easily install extra JRE from host #5
Comments
Would love the possibility to use multiple JDK's with Flatpak Eclipse. Not figured out, how to use a different version than the one bundled and ship with the Flatpak package. |
This would be a showstopper for me too, but @mickaelistria correct me if I'm wrong: I can easily select and add the following paths in my Linux Mint 18.3 (based on Ubuntu 16.04): BTW: @mbooth101 please document the /run/host/... thing, perhaps it's the solution to my #15 issue... |
I believe @mickaelistria is using Fedora, where they are symlinks.
Accessing the host filesystem from sandbox is fully documented at flatpak.org: https://docs.flatpak.org/en/latest/sandbox-permissions.html#filesystem-access Relevant quote:
|
I've been facing this problem of symbolic links not dereferencing as well. I tried to Importing the same symlinks through I've noticed that the Eclipse uses the the host's filepicker dialog in former and the sandbox's filepicker in the latter. |
I think another problem related to symlinks and extra JREs is the following: #18. |
I can now browse the directory in Installed JREs and it automatically translates to the Flatpak redirect paths. |
I'm using Eclipse SDK Flatpak, and I have multiple versions of Java installed locally (8 and 13 in the host, 11 in Flatpak).
I'd like to configure the Eclipse SDK so that Java 8 and Java 13 are installed (to more easily test backward and forward compatibility of the projects I'm developing).
However, when inside the Installed JRE preference page and trying to add path to those host JREs, I cannot find those path. Then I remember going into
/run/host/usr/lib
but I see the symbolic links can't be selected, so I'm forced to use the exact version, which is likely to become incorrect on next update.The text was updated successfully, but these errors were encountered: