Well, I celebrated too soon... It appears that with Live Errors, the compile process proceeds part way, and then errors out.
To review:
- In Build->Java Options->Compiler->Other Options, I am using these options:
--module-path "C:\Program Files\Java\javafx-sdk-17.0.2\lib" --add-modules javafx.controls,javafx.web,javafx.swing - In Build->Java Options->Live Errors, I have selected the Use "Other Options" from Compiler Tab check box.
- I'm having difficulty with Live Errors
With the above setup, certain types of errors are being highlighted by Live Errors, but not all. For example:
- If I type gibberish text, it will get flagged
- Most syntax errors get flagged
- If I don't declare a variable type, it will not get flagged
- If I don't declare a thrown exception, it will not get flagged
The Java compiler is a multi-pass compiler, so I am guessing that the early passes are working normally, but a later pass fails.
When I activate Live Errors (e.g. type a character and delete it), (a) the
Output tab shows nothing, and (b) my
Message List tab might have some legitimately flagged errors, but these are always the last three errors:
- module not found: javafx.swing
- module not found: javafx.controls
- module not found: javafx.web
I've spent a lot of time checking the options I put into
Build->Java Options->Compiler->Other Options, and comparing them to what I use successfully when I use
javac on the command line, so I don't think that is the problem.
I tried a couple of experiments at the system command line:
C:\Directory\to\Project\and\module>javac --module-path "C:\Program Files\Java\javafx-sdk-17.0.2\lib" --add-modules javafx.controls,javafx.web,javafx.swing KnownGoodCode.java
C:\Directory\to\Project\and\module>javac --module-path "C:\Program Files\Java\javafx-sdk-17.0.2\libx" --add-modules javafx.controls,javafx.web,javafx.swing KnownGoodCode.java
error: module not found: javafx.swing
error: module not found: javafx.controls
error: module not found: javafx.web
3 errors
C:\Directory\to\Project\and\module>
(Notice the bogus path in the second command issued)
I don't have much visibility into the issue, so I can't give you much more help.