Confused about status of JFX+JRE cobundling
igor.nekrestyanov at oracle.com
Mon Jun 18 22:30:41 PDT 2012
On 6/18/12 10:23 PM, Daniel Zwolenski wrote:
> Yep, that clears things up, thanks!
> * In 7u6 JavaFX will not be automatically added to classpath
> (neither for javac not java launcher).
> I don't understand this though. Why is it not added, and what
> advantage is there at all to co-bundling if JFX is not on the classpath?
This is current limitation.
It had been discussed for a while and various concerns had been raised
as this impacts all existing apps and not just javafx apps
(security, compatibility, etc.). Hopefully this will be addressed in one
of future releases.
This is not the only jar in the JRE that is not on the bootclasspath.
E.g. none of deployment jars are ...
To me biggest benefits are:
* JavaFX effectively be preinstalled on most of the systems that
* No separate installation => fewer problems due to installer bugs
&& issues caused by Java/JavaFX mix&match
* SDK is bundled => much easier for IDEs to support JavaFX development
* Easier to build native bundles -- in the current implementation
runtime is defined by JDK being used
* no need in separate Maven module for JavaFX :)
List is not complete, these are just few top of my head and seems
important to me,
More information about the openjfx-dev