Confused about status of JFX+JRE cobundling

Tom Schindl tom.schindl at
Tue Jun 19 00:49:32 PDT 2012

Am 19.06.12 09:37, schrieb Igor Nekrestyanov:
> On 6/19/12 12:15 AM, Tom Schindl wrote:
>> * the unbalanced decision to not provide SDK-Drops as zips makes
>>    repackaging for different platforms complex
> What other platforms you are referring to? Other Linux distros?

No I'm talking about windows and mac. Say I'm a win32 user and want to
package an application for users on mac and win32. How would you advise
to do so?

Answer: Buy a Mac because you don't get access to JavaFX jar and native
libs without out it!

>> there is now a missmatch between those not wanting to install a JDK
> update and use the JavaFX-SDK because native packaging with fx:deploy
> task is not working for them.
> What is the problem with having multiple versions of JDK on the system?
> Unlike runtime these are fully independent ...

JavaFX previews are shipped on a very regular base so now with the
co-bundleing I'm downloading the whole JDK all the time although I'm
only interested in the latest JavaFX.

>> Is it really such a big problem to find out java.home for the ant-task
> and packaging this up? Just asking
> Current native packaging support makes a lot of simplifying assumptions
> on bundle configuration as we do not want to expose too many APIs in a rush
> (and we likely will provide more flexible APIs in a future for use cases
> that will be popular).
> Decision to use current JDK cobundle as a source for native bundle is
> one of these simplifications. It was not motivation for cobundling Java
> and JavaFX in JDK,
> it is another way - because JDK is true cobundle we had option to
> simplify things.
> -igor


B e s t S o l u t i o n . a t                        EDV Systemhaus GmbH
tom schindl                 geschäftsführer/CEO
eduard-bodem-gasse 5-7/1   A-6020 innsbruck     fax      ++43 512 935833                      phone    ++43 512 935834

More information about the openjfx-dev mailing list