I got a tar file, which, when expanded, gave me an app. I launched the app (who's name I do not recall), which proceeded to download a JRE...somewhere, and gave me (I think) another app.
I launched that app, it, too, downloaded another JRE (so it said), and then launched the Ensemble app.
The Ensemble app worked fine, but none of the source code from the samples was visible. I don't know if that's a packaging issue or not.
All files related to it are kept in $HOME/.jdeploy
The observation that it downloaded 2 JREs (one for the installer and the other for the app) is a rough edge that will be fixed in an upcoming release. The reason is that the installer itself is an app that was bundled by jDeploy. It required a JRE, but didn't require JavaFX. When you, then launched the actual app, which was installed, it needed JavaFX, so couldn't use the JRE that was installed for the installer app, so it downloaded a JRE with JavaFX.
I will be optimizing this so that the "installer app" will try to use a JRE that meets both the installer requirements and app requirements so it only needs to download one JRE.
I got a tar file, which, when expanded, gave me an app. I launched the app (who's name I do not recall), which proceeded to download a JRE...somewhere, and gave me (I think) another app.
I launched that app, it, too, downloaded another JRE (so it said), and then launched the Ensemble app.
The Ensemble app worked fine, but none of the source code from the samples was visible. I don't know if that's a packaging issue or not.
Where did it install the JREs?