This fixes the build issue on my side, due to no JDK (only a JRE) being installed for the build.
I'm not completely convinced the resulting flatpak is as small as needed, though: when I list the content of ~/.local/share/flatpak/app/my.example.HelloTemplate/current/active/files/HelloTemplate after installing the flatpak, I see the following:
~/.local/share/flatpak/app/my.example.HelloTemplate/current/active/files$ tree -L 1
.
├── HelloTemplate
├── jdk
├── jre
└── manifest.json
Ideally, only the JRE should be shipped in the flatpak (it's all that's needed to run the app, afterall). The JDK is only needed when building the flatpak.
This fixes the build issue on my side, due to no JDK (only a JRE) being installed for the build.
I'm not completely convinced the resulting flatpak is as small as needed, though: when I list the content of `~/.local/share/flatpak/app/my.example.HelloTemplate/current/active/files/HelloTemplate` after installing the flatpak, I see the following:
```
~/.local/share/flatpak/app/my.example.HelloTemplate/current/active/files$ tree -L 1
.
├── HelloTemplate
├── jdk
├── jre
└── manifest.json
```
Ideally, only the JRE should be shipped in the flatpak (it's all that's needed to run the app, afterall). The JDK is only needed when building the flatpak.