Co-bundling for christmas

Tom Schindl tom.schindl at
Fri Dec 23 01:33:21 PST 2011

Am 23.12.11 10:24, schrieb Roman Kennke:
> Hi all,
>>    2. We lose *control over versions* in use. Since the Java auto-updater
>>    is always pulling down the latest version, there is no way to pin an
>>    application to a specific JFX version.
> To me this is the most important disadvantage. For enterprises it is
> very important to have control over versions, autoupdate is ususally the
> first thing that gets disabled.
> My opinion is that JavaFX should not be bundled with the JRE and/or
> installed system wide, but should be the developers responsibility to
> bundle with the application, together with any other libraries.

With jigsaw you have this feature whether JavaFX is bundled with the
full JRE download & update cycle or not. If you require 2.0.2 in your
app and even if there's a 2.1, 3.0, ... available in your local module
repo, you're app will resolve 2.0.2.

It's like it is today if you'd use OSGi with the difference that using
multiple versions of the same module in one application is not possible
(or at least not all use cases are supported).

I think the only thing you are not able to control is which VM is used.


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