Chuck, you are right, the "requires phrase" was the only step needed. Perhaps,
to eliminate manual intervention, this can be automated at some future point.
On Sunday, August 16, 2020, 6:18:12 AM GMT+4:30, Chuck Davis
wrote:
I think all you need is the requires phrase.
On Sat, Aug 15,
I think all you need is the requires phrase.
On Sat, Aug 15, 2020 at 6:42 PM HRH wrote:
> Thanks, that was the missing part that caused the error. Do I need to
> revise the statement that begins with the "opens" directive? I took the
> liberty and changed it. The module file looks as follow:
>
>
Thanks, that was the missing part that caused the error. Do I need to revise
the statement that begins with the "opens" directive? I took the liberty and
changed it. The module file looks as follow:
module org.openjfx.fxmavenfxml {
requires javafx.controls;
requires javafx.fxml;
requ
Did you revise the module file?
On Sat, Aug 15, 2020 at 11:34 AM HRH wrote:
> Hi,
>
> I had an FXML file that was working fine until I added an UI component
> "WebView". The in the FXML file
> marked as an error because somehow the javafx.web from the JavaFx\Lib is
> not seen. I have already mo
Hi,
I had an FXML file that was working fine until I added an UI component
"WebView". The in the FXML file marked as
an error because somehow the javafx.web from the JavaFx\Lib is not seen. I have
already modified the POM file to include this dependency as follow alas the
FXMLLoader.load() fai
