Re: Announcing EA builds of standalone JavaFX SDK

[Michael Paus]

Hi,
a few days ago I was informed in a private e-mail from Bernhard Lutzmann 
how the problem with Eclipse described below can be solved without 
having to provide a module-info.java. The problem in Eclipse is that, 
although the JavaFX jars are explicitly put on the module path in the 
build configuration, this is not copied over to the runtime 
configuration. So each time when you create a new runtime configuration 
you have to go to the dependencies tab in the runtime configuration 
editor and manually remove the JavaFX jars form the classpath and then 
add them one by one to the module path again. I consider this annoying 
behaviour a bug and have thus filed a corresponding bug report.




Michael

Am 09.05.18 um 13:39 schrieb Michael Paus:

Hi,
I investigated the issue of using the standalone JavaFX SDK inside of 
an IDE (Eclipse and IntelliJ) a little bit further. For this purpose I 
used a simple single-class JavaFX program (actually the one which 
Johan used too).


I started with Eclipse, created a simple Java project, added the JFX 
jars to the module path and added the --add-modules command to the 
runtime configuration. The result is: this works at compile time but 
not at runtime.


Then I tried the same with IntelliJ. (I have to admit though that I 
have never seriously used IntelliJ before.) I created the project, 
added the dependencies and configured the runtime. The result is: the 
same error as in Eclipse.


The advantage of IntelliJ though is that it directly shows you the 
command line which was created to launch the application. The problem 
seems to be that IntelliJ (in the same way as Eclipse) just puts the 
JavaFX dependencies on the classpath and not on the module path. The 
only way I found to fix this was to add a module-info.java to the 
project.


module projavafx.helloearthrise.ui {
    requires javafx.graphics;
    requires javafx.controls;
    exports projavafx.helloearthrise.ui;
}

After that you don't need the --add-modules command anymore.

After adding this the setup immediately worked in IntelliJ. In Eclipse 
however the program could now be launched and there was no error or 
warning but the program just hangs and does not show anything on the 
screen. By looking at the generated command line via "ps -ef | grep 
java" I found that Eclipse is adding this option 
"-XstartOnFirstThread" which makes the program hang. There is a switch 
in the Eclipse runtime configuration dialog, which is selected by 
default, and which causes Eclipse to use this option when it thinks it 
is launched with SWT. This is caused by the fact that I have created a 
library (like Nir suggested) into which I put all jars of the JavaFX 
SDK, also the javafx-swt.jar one although it is not needed here. This 
has never been a problem before the split between JDK and JFX. This 
problem can be fixed by either switching off the startOnFirstThread 
option in the runtime configuration or by just not adding the 
javafx-swt.jar.


So, my conclusion for the moment is that you can only use the split 
JDK/JFX in Eclipse/IntelliJ when your main project has a 
module-info.java. This may be a problem if you are not yet ready or 
willing to modularize your application.


If somebody knows a trick to get around this limitation I'd be happy 
to here about it.


Michael


Am 08.05.18 um 14:39 schrieb Michael Paus:

Am 08.05.18 um 14:27 schrieb Tom Schindl:

[...]

3. How do you properly configure an Eclipse (the latest 4.7.3a) 
project

to use this module path. Adding the OpenJDK was no problem but how do
you add the module path for JavaFX? I failed on that.

You just open the Java Build Path-Properties-Page on the project and 
add

the external jars, not?

Tom


That's one of the ways I tried it but ...

1. is that the intended way of doing it? On the command line you just 
specify a single folder.


2. I did this and it resolved all dependencies at compile time but I 
got an exception at runtime


Error occurred during initialization of boot layer
java.lang.module.FindException: Module javafx.fxml not found

although I also added

--add-modules=javafx.fxml,javafx.controls,javafx.web,javafx.media

as VM arguments.

Re: Announcing EA builds of standalone JavaFX SDK

[Michael Paus]

Hi,
I investigated the issue of using the standalone JavaFX SDK inside of an 
IDE (Eclipse and IntelliJ) a little bit further. For this purpose I used 
a simple single-class JavaFX program (actually the one which Johan used 
too).


I started with Eclipse, created a simple Java project, added the JFX 
jars to the module path and added the --add-modules command to the 
runtime configuration. The result is: this works at compile time but not 
at runtime.


Then I tried the same with IntelliJ. (I have to admit though that I have 
never seriously used IntelliJ before.) I created the project, added the 
dependencies and configured the runtime. The result is: the same error 
as in Eclipse.


The advantage of IntelliJ though is that it directly shows you the 
command line which was created to launch the application. The problem 
seems to be that IntelliJ (in the same way as Eclipse) just puts the 
JavaFX dependencies on the classpath and not on the module path. The 
only way I found to fix this was to add a module-info.java to the project.


module projavafx.helloearthrise.ui {
    requires javafx.graphics;
    requires javafx.controls;
    exports projavafx.helloearthrise.ui;
}

After that you don't need the --add-modules command anymore.

After adding this the setup immediately worked in IntelliJ. In Eclipse 
however the program could now be launched and there was no error or 
warning but the program just hangs and does not show anything on the 
screen. By looking at the generated command line via "ps -ef | grep 
java" I found that Eclipse is adding this option "-XstartOnFirstThread" 
which makes the program hang. There is a switch in the Eclipse runtime 
configuration dialog, which is selected by default, and which causes 
Eclipse to use this option when it thinks it is launched with SWT. This 
is caused by the fact that I have created a library (like Nir suggested) 
into which I put all jars of the JavaFX SDK, also the javafx-swt.jar one 
although it is not needed here. This has never been a problem before the 
split between JDK and JFX. This problem can be fixed by either switching 
off the startOnFirstThread option in the runtime configuration or by 
just not adding the javafx-swt.jar.


So, my conclusion for the moment is that you can only use the split 
JDK/JFX in Eclipse/IntelliJ when your main project has a 
module-info.java. This may be a problem if you are not yet ready or 
willing to modularize your application.


If somebody knows a trick to get around this limitation I'd be happy to 
here about it.


Michael


Am 08.05.18 um 14:39 schrieb Michael Paus:

Am 08.05.18 um 14:27 schrieb Tom Schindl:

[...]


3. How do you properly configure an Eclipse (the latest 4.7.3a) project
to use this module path. Adding the OpenJDK was no problem but how do
you add the module path for JavaFX? I failed on that.


You just open the Java Build Path-Properties-Page on the project and add
the external jars, not?

Tom


That's one of the ways I tried it but ...

1. is that the intended way of doing it? On the command line you just 
specify a single folder.


2. I did this and it resolved all dependencies at compile time but I 
got an exception at runtime


Error occurred during initialization of boot layer
java.lang.module.FindException: Module javafx.fxml not found

although I also added

--add-modules=javafx.fxml,javafx.controls,javafx.web,javafx.media

as VM arguments.

Re: Announcing EA builds of standalone JavaFX SDK

[Michael Paus]

Am 08.05.18 um 23:55 schrieb Nir Lisker:

Thanks Kevin, that's good to hear.

Michael, adding the external jars as single entries is the simplest 
and most granular way, but you can also define a library from those 
jars and then add that single library to any project:


1. Add Library...
2. User Library
3. User Libraries...
4. New... (give it a name)
5. Add External JARs... (add all the jars)
6. OK/Apply everything.

This creates a single entry in the .classpath:

    path="org.eclipse.jdt.USER_LIBRARY/library_name">


This should be the parallel to specifying a single folder from the 
command line.

I'll give that a try in the morning.


As for the runtime issue, is it finding the other modules?
No, if I do not specify javafx.fxml it complains about the next one. I 
also tried moving all jars to the classpath instead of the module path. 
Again this resolves the compile time dependencies but results in an 
error at runtime. Since Java 9 Eclipse has really become a mess.


- Nir

On Tue, May 8, 2018 at 3:39 PM, Michael Paus > wrote:


Am 08.05.18 um 14:27 schrieb Tom Schindl:

[...]

3. How do you properly configure an Eclipse (the latest
4.7.3a) project
to use this module path. Adding the OpenJDK was no problem
but how do
you add the module path for JavaFX? I failed on that.

You just open the Java Build Path-Properties-Page on the
project and add
the external jars, not?

Tom


That's one of the ways I tried it but ...

1. is that the intended way of doing it? On the command line you
just specify a single folder.

2. I did this and it resolved all dependencies at compile time but
I got an exception at runtime

Error occurred during initialization of boot layer
java.lang.module.FindException: Module javafx.fxml not found

although I also added

--add-modules=javafx.fxml,javafx.controls,javafx.web,javafx.media

as VM arguments.

Re: Announcing EA builds of standalone JavaFX SDK

[Nir Lisker]

Thanks Kevin, that's good to hear.

Michael, adding the external jars as single entries is the simplest and
most granular way, but you can also define a library from those jars and
then add that single library to any project:

1. Add Library...
2. User Library
3. User Libraries...
4. New... (give it a name)
5. Add External JARs... (add all the jars)
6. OK/Apply everything.

This creates a single entry in the .classpath:



This should be the parallel to specifying a single folder from the command
line.

As for the runtime issue, is it finding the other modules?

- Nir

On Tue, May 8, 2018 at 3:39 PM, Michael Paus  wrote:

> Am 08.05.18 um 14:27 schrieb Tom Schindl:
>
> [...]
>>
>> 3. How do you properly configure an Eclipse (the latest 4.7.3a) project
>>> to use this module path. Adding the OpenJDK was no problem but how do
>>> you add the module path for JavaFX? I failed on that.
>>>
>>> You just open the Java Build Path-Properties-Page on the project and add
>> the external jars, not?
>>
>> Tom
>>
>
> That's one of the ways I tried it but ...
>
> 1. is that the intended way of doing it? On the command line you just
> specify a single folder.
>
> 2. I did this and it resolved all dependencies at compile time but I got
> an exception at runtime
>
> Error occurred during initialization of boot layer
> java.lang.module.FindException: Module javafx.fxml not found
>
> although I also added
>
> --add-modules=javafx.fxml,javafx.controls,javafx.web,javafx.media
>
> as VM arguments.
>
>

Re: Announcing EA builds of standalone JavaFX SDK

[Jonathan Giles]

Congrats to Kevin and team on this milestone!

-- Jonathan
(Tapped on a touch device)

On Mon, 7 May 2018, 4:01 PM Kevin Rushforth, 
wrote:

> I am pleased to announce the first Early Access build of a standalone
> JavaFX SDK [1]. You can download it and run it using OpenJDK 10 or an
> OpenJDK 11 EA build.
>
> If your application is in an unnamed module (i.e., your app is on the
> classpath), you can run your application as follows, after unzipping the
> SDK bundle for your platform.
>
> $ java --module-path $PATH_TO_FX/javafx-sdk-11
> --add-modules=javafx.controls,javafx.fxml MyApp
>
> This assumes you don't need media or web. If you do, then add those
> modules, too. Note that since javafx.web "requires transitive
> javafx.controls", you can omit javafx.controls if you add javafx.web.
>
> If you are running a modular application, then you don't need the
> "--add-modules" option.
>
> Note that this is a stepping stone to javafx modules in a repository
> like Maven.
>
> Please test your applications with the SDK and give us feedback.
>
> Thanks.
>
> -- Kevin
>
> [1] http://jdk.java.net/openjfx/
>
>

Re: Announcing EA builds of standalone JavaFX SDK

[Kevin Rushforth]

On 5/8/2018 5:01 AM, Michael Paus wrote:

Hi Kevin,
that's a great achievement. I have a few questions/remarks though:

1. On the announcement page I assume the license agreement should not 
read
"These binaries are provided under the GNU General Public License 
."

but instead should read
"These early-access, open-source builds are provided under the GNU 
General Public License, version 2, with the Classpath Exception 
."
With or without classpath exception makes a big difference. (The 
actual link is already the same anyway.)


I will get this fixed to match the JDK 11 EA text.


2. I can confirm that a simple program from the command line works 
nicely on my MacBook Pro Retina but I had to add "/lib" to the module 
path to get it working.


Yes, adding the javafx-sdk-11/lib to the module-path is a required step.

Thanks.

-- Kevin




3. How do you properly configure an Eclipse (the latest 4.7.3a) 
project to use this module path. Adding the OpenJDK was no problem but 
how do you add the module path for JavaFX? I failed on that.


Michael

Am 08.05.18 um 01:00 schrieb Kevin Rushforth:
I am pleased to announce the first Early Access build of a standalone 
JavaFX SDK [1]. You can download it and run it using OpenJDK 10 or an 
OpenJDK 11 EA build.


If your application is in an unnamed module (i.e., your app is on the 
classpath), you can run your application as follows, after unzipping 
the SDK bundle for your platform.


$ java --module-path $PATH_TO_FX/javafx-sdk-11 
--add-modules=javafx.controls,javafx.fxml MyApp


This assumes you don't need media or web. If you do, then add those 
modules, too. Note that since javafx.web "requires transitive 
javafx.controls", you can omit javafx.controls if you add javafx.web.


If you are running a modular application, then you don't need the 
"--add-modules" option.


Note that this is a stepping stone to javafx modules in a repository 
like Maven.


Please test your applications with the SDK and give us feedback.

Thanks.

-- Kevin

[1] http://jdk.java.net/openjfx/

Re: Announcing EA builds of standalone JavaFX SDK

[Michael Paus]

Am 08.05.18 um 14:37 schrieb Paul Ray Russell:

V. pleased to say it's working for me. It builds using our current Maven
build ( which is targeted in Maven at JDK 9)

  
 org.apache.maven.plugins
 maven-compiler-plugin
 3.6.2
 
 1.9
 1.9
 
 -Xlint:unchecked
 
 
 

Trying to set a 1.11 release will give the Maven error:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile
(default-compile) on project KattRunOnTheTide: Fatal error compiling:
error: invalid target release: 1.11 -> [Help 1]

Have you tried using the latest Maven compiler plugin 3.7.0 ?

Re: Announcing EA builds of standalone JavaFX SDK

[Michael Paus]

Am 08.05.18 um 14:27 schrieb Tom Schindl:

[...]


3. How do you properly configure an Eclipse (the latest 4.7.3a) project
to use this module path. Adding the OpenJDK was no problem but how do
you add the module path for JavaFX? I failed on that.


You just open the Java Build Path-Properties-Page on the project and add
the external jars, not?

Tom


That's one of the ways I tried it but ...

1. is that the intended way of doing it? On the command line you just 
specify a single folder.


2. I did this and it resolved all dependencies at compile time but I got 
an exception at runtime


Error occurred during initialization of boot layer
java.lang.module.FindException: Module javafx.fxml not found

although I also added

--add-modules=javafx.fxml,javafx.controls,javafx.web,javafx.media

as VM arguments.

Re: Announcing EA builds of standalone JavaFX SDK

[Paul Ray Russell]

ChainImpl.dispatchEvent(EventDispatchChainImpl.java:114)
at
javafx.base/com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56)
at
javafx.base/com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114)
at
javafx.base/com.sun.javafx.event.EventUtil.fireEventImpl(EventUtil.java:74)
at
javafx.base/com.sun.javafx.event.EventUtil.fireEvent(EventUtil.java:54)
at javafx.base/javafx.event.Event.fireEvent(Event.java:198)
at
javafx.graphics/javafx.scene.Scene$MouseHandler.process(Scene.java:3851)
at
javafx.graphics/javafx.scene.Scene$MouseHandler.access$1200(Scene.java:3579)
at
javafx.graphics/javafx.scene.Scene.processMouseEvent(Scene.java:1849)
at
javafx.graphics/javafx.scene.Scene$ScenePeerListener.mouseEvent(Scene.java:2588)
at
javafx.graphics/com.sun.javafx.tk.quantum.GlassViewEventHandler$MouseEventNotification.run(GlassViewEventHandler.java:397)
at
javafx.graphics/com.sun.javafx.tk.quantum.GlassViewEventHandler$MouseEventNotification.run(GlassViewEventHandler.java:295)
at java.base/java.security.AccessController.doPrivileged(Native
Method)
at
javafx.graphics/com.sun.javafx.tk.quantum.GlassViewEventHandler.lambda$handleMouseEvent$2(GlassViewEventHandler.java:434)
at
javafx.graphics/com.sun.javafx.tk.quantum.QuantumToolkit.runWithoutRenderLock(QuantumToolkit.java:389)
at
javafx.graphics/com.sun.javafx.tk.quantum.GlassViewEventHandler.handleMouseEvent(GlassViewEventHandler.java:433)
at
javafx.graphics/com.sun.glass.ui.View.handleMouseEvent(View.java:556)
at javafx.graphics/com.sun.glass.ui.View.notifyMouse(View.java:942)
at
javafx.graphics/com.sun.glass.ui.win.WinApplication._runLoop(Native Method)
at
javafx.graphics/com.sun.glass.ui.win.WinApplication.lambda$runLoop$3(WinApplication.java:175)
at java.base/java.lang.Thread.run(Thread.java:832)

I hope this helps. Looking forwards to a pure Maven build.

Best,
Paul

On 8 May 2018 at 11:30, <openjfx-dev-requ...@openjdk.java.net> wrote:

> Send openjfx-dev mailing list submissions to
> openjfx-dev@openjdk.java.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mail.openjdk.java.net/mailman/listinfo/openjfx-dev
> or, via email, send a message with subject or body 'help' to
> openjfx-dev-requ...@openjdk.java.net
>
> You can reach the person managing the list at
> openjfx-dev-ow...@openjdk.java.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of openjfx-dev digest..."
>
>
> Today's Topics:
>
>1. Announcing EA builds of standalone JavaFX SDK (Kevin Rushforth)
>2. Re: [11] RFR JDK-8202199 : Provide public, unsupported API
>   for FX Swing interop (Prasanta Sadhukhan)
>3. Re: [11] RFR JDK-8202199 : Provide public, unsupported API
>   for FX Swing interop (Ali Ebrahimi)
>4. Re: Announcing EA builds of standalone JavaFX SDK (Johan Vos)
>5. Re: [11] RFR JDK-8202199 : Provide public, unsupported API
>   for FX Swing interop (Prasanta Sadhukhan)
>6. Re: [11] RFR JDK-8202199 : Provide public, unsupported API
>   for FX Swing interop (Alan Bateman)
>
>
> --
>
> Message: 1
> Date: Mon, 7 May 2018 16:00:19 -0700
> From: Kevin Rushforth <kevin.rushfo...@oracle.com>
> To: "openjfx-dev@openjdk.java.net" <openjfx-dev@openjdk.java.net>
> Subject: Announcing EA builds of standalone JavaFX SDK
> Message-ID: <8ae613b7-bac6-fa44-94e4-7490b0726...@oracle.com>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> I am pleased to announce the first Early Access build of a standalone
> JavaFX SDK [1]. You can download it and run it using OpenJDK 10 or an
> OpenJDK 11 EA build.
>
> If your application is in an unnamed module (i.e., your app is on the
> classpath), you can run your application as follows, after unzipping the
> SDK bundle for your platform.
>
> $ java --module-path $PATH_TO_FX/javafx-sdk-11
> --add-modules=javafx.controls,javafx.fxml MyApp
>
> This assumes you don't need media or web. If you do, then add those
> modules, too. Note that since javafx.web "requires transitive
> javafx.controls", you can omit javafx.controls if you add javafx.web.
>
> If you are running a modular application, then you don't need the
> "--add-modules" option.
>
> Note that this is a stepping stone to javafx modules in a repository
> like Maven.
>
> Please test your applications with the SDK and give us feedback.
>
> Thanks.
>
> -- Kevin
>
> [1] http://jdk.java.net/openjfx/
>
>
>
> ---

Re: Announcing EA builds of standalone JavaFX SDK

[Tom Schindl]

[...]

> 3. How do you properly configure an Eclipse (the latest 4.7.3a) project
> to use this module path. Adding the OpenJDK was no problem but how do
> you add the module path for JavaFX? I failed on that.
> 

You just open the Java Build Path-Properties-Page on the project and add
the external jars, not?

Tom

Re: Announcing EA builds of standalone JavaFX SDK

[Michael Paus]

Hi Kevin,
that's a great achievement. I have a few questions/remarks though:

1. On the announcement page I assume the license agreement should not read
"These binaries are provided under the GNU General Public License 
."

but instead should read
"These early-access, open-source builds are provided under the GNU 
General Public License, version 2, with the Classpath Exception 
."
With or without classpath exception makes a big difference. (The actual 
link is already the same anyway.)


2. I can confirm that a simple program from the command line works 
nicely on my MacBook Pro Retina but I had to add "/lib" to the module 
path to get it working.


3. How do you properly configure an Eclipse (the latest 4.7.3a) project 
to use this module path. Adding the OpenJDK was no problem but how do 
you add the module path for JavaFX? I failed on that.


Michael

Am 08.05.18 um 01:00 schrieb Kevin Rushforth:
I am pleased to announce the first Early Access build of a standalone 
JavaFX SDK [1]. You can download it and run it using OpenJDK 10 or an 
OpenJDK 11 EA build.


If your application is in an unnamed module (i.e., your app is on the 
classpath), you can run your application as follows, after unzipping 
the SDK bundle for your platform.


$ java --module-path $PATH_TO_FX/javafx-sdk-11 
--add-modules=javafx.controls,javafx.fxml MyApp


This assumes you don't need media or web. If you do, then add those 
modules, too. Note that since javafx.web "requires transitive 
javafx.controls", you can omit javafx.controls if you add javafx.web.


If you are running a modular application, then you don't need the 
"--add-modules" option.


Note that this is a stepping stone to javafx modules in a repository 
like Maven.


Please test your applications with the SDK and give us feedback.

Thanks.

-- Kevin

[1] http://jdk.java.net/openjfx/

Re: Announcing EA builds of standalone JavaFX SDK

[John-Val Rose]

Thanks very much Kevin.

This is a great step forward and will make all of our lives easier.

Graciously,

John-Val Rose

> On 8 May 2018, at 17:43, Johan Vos  wrote:
> 
> Hi Kevin,
> 
> Excellent work.
> I confirm this is working for me.
> 
> Java: openjdk 11-ea+12 for Linux
> App from
> https://github.com/gluonhq/projavafx9/tree/master/chapter1/HelloEarthRise/src/main/java/projavafx/helloearthrise/ui
> (on
> classpath)
> 
> - Johan
> 
> On Tue, May 8, 2018 at 1:11 AM Kevin Rushforth 
> wrote:
> 
>> I am pleased to announce the first Early Access build of a standalone
>> JavaFX SDK [1]. You can download it and run it using OpenJDK 10 or an
>> OpenJDK 11 EA build.
>> 
>> If your application is in an unnamed module (i.e., your app is on the
>> classpath), you can run your application as follows, after unzipping the
>> SDK bundle for your platform.
>> 
>> $ java --module-path $PATH_TO_FX/javafx-sdk-11
>> --add-modules=javafx.controls,javafx.fxml MyApp
>> 
>> This assumes you don't need media or web. If you do, then add those
>> modules, too. Note that since javafx.web "requires transitive
>> javafx.controls", you can omit javafx.controls if you add javafx.web.
>> 
>> If you are running a modular application, then you don't need the
>> "--add-modules" option.
>> 
>> Note that this is a stepping stone to javafx modules in a repository
>> like Maven.
>> 
>> Please test your applications with the SDK and give us feedback.
>> 
>> Thanks.
>> 
>> -- Kevin
>> 
>> [1] http://jdk.java.net/openjfx/
>> 
>> 

Re: Announcing EA builds of standalone JavaFX SDK

[Johan Vos]

Hi Kevin,

Excellent work.
I confirm this is working for me.

Java: openjdk 11-ea+12 for Linux
App from
https://github.com/gluonhq/projavafx9/tree/master/chapter1/HelloEarthRise/src/main/java/projavafx/helloearthrise/ui
(on
classpath)

- Johan

On Tue, May 8, 2018 at 1:11 AM Kevin Rushforth 
wrote:

> I am pleased to announce the first Early Access build of a standalone
> JavaFX SDK [1]. You can download it and run it using OpenJDK 10 or an
> OpenJDK 11 EA build.
>
> If your application is in an unnamed module (i.e., your app is on the
> classpath), you can run your application as follows, after unzipping the
> SDK bundle for your platform.
>
> $ java --module-path $PATH_TO_FX/javafx-sdk-11
> --add-modules=javafx.controls,javafx.fxml MyApp
>
> This assumes you don't need media or web. If you do, then add those
> modules, too. Note that since javafx.web "requires transitive
> javafx.controls", you can omit javafx.controls if you add javafx.web.
>
> If you are running a modular application, then you don't need the
> "--add-modules" option.
>
> Note that this is a stepping stone to javafx modules in a repository
> like Maven.
>
> Please test your applications with the SDK and give us feedback.
>
> Thanks.
>
> -- Kevin
>
> [1] http://jdk.java.net/openjfx/
>
>