Flatpak is a relatively new and distribution independent package manager with some nice features. In some cases these features can have unexpected effects that might lead to some headaches if these features are not known and handled appropriately.
When one tries to execute programs inside Eclipse that depend on system components
one might find a surprise. When for instance the program in question executes bash
commands an irritating message might appear: command not found
.
The reason for this is that programs that are installed inside Flatpak are also executed in Flatpak in a sandboxed environment. This means that the program does not have access to unnecessary system components. Therefore, the program needs to be executed outside the sandbox. Genereally speaking programs inside Flatpak have access to files inside the current user home folder.
An additional console has to be used in this case instead of the Run As
option of Eclipse. The console provided by Eclipse cannot used for this as it also
has these access limitations. In order to execute the project one has to go into the
project's folder and execute a command like this: mvn exec:java -Dexec.mainClass=net.splitcells.example.Clazz
-
debugging
-
Alternative way to break out of sandbox legally without compromising security and avoiding not wanted dependencies.