Deployment: native application bundles

[Daniel Zwolenski]

Very cool!

The Ensemble MSI install worked for me on Windows 7 no problems. I haven't
tried building my own app as yet though.

It installed into 'C:\Users\zonski\AppData\Local\Ensemble2'. Installing
into Program Files is probably more correct on windows. Is this 'appdata'
the intended final location, or is this just for getting it all running for
now?

Is the source code available for this at all? If not, I'm very interested
in how the 'exe' launcher code looks. Is this code you've written or part
of one of the tools you've made use of? I'm particularly interested to see
how it starts the app - does it just kick off another process on the
executable jar via something like 'java -jar ensemble.jar' or does it try
to run the Java app within it's own 'exe' process somehow (I'm assuming the
later?).

I notice also that the jfx DLLs have been copied straight into the
'jre/bin' directory. Is this how you see all native dependencies playing
out, i.e. if my application uses other native libraries how do I package
them into the build and where will they be installed to in the extracted
directory?

Very, very nice start to this all!

Cheers,
Dan


On Fri, Jun 15, 2012 at 5:16 PM, Igor Nekrestyanov <
igor.nekrestyanov at oracle.com> wrote:

> Hi,
>
> One thing we are adding to JavaFX packaging tools in 2.2 is ability to
> produce native application bundles:
>    https://blogs.oracle.com/**talkingjavadeployment/entry/**
> native_packaging_for_javafx<https://blogs.oracle.com/talkingjavadeployment/entry/native_packaging_for_javafx>
>
> We are not seeing this as the only way to deploy JavaFX applications --
> webstart, embedded applications
> and doubleclickable jars are first class citizens (and it would be great
> to explore other options).
> But we hope it might be good option for many deployment scenarios.
>
> Please give it a try and provide feedback (and report bugs of course),
>
> -igor
>