I'm trying to fix the error badges on JavaFX test code.
Most of the imports giving "package is declared in unnamed module" error. I came across with https://github.com/BetterCloud/vault-java-driver which has the same issue, though it's build script is more reasonable. The interesting thing is, if I remove the module-info.java from the main sourceset everything sets to be right.
I've read halfway through https://sormuras.github.io/blog/2018-09-11-testing-in-the-modular-world.html and it seems for testing these projects are reverting back from modular java to classpath java (correct me if I'm wrong).
As far as I've checked (placed a breakpoint in the code) I do not see that NetBeans is requesting modulepath for the test code, still it threats that code if it was modular. At least that's what I think.
As we have some good folks here who are really into the compiler/java business, I'd ask, how shall we handle such test sourcesets?
Is it a bug in NetBeans that only if the main sourceset is modular, then the whole project would be treated like that?
So some guidance would be really appreciated. -- Laszlo Kishalmi --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
