When compiling my project I get a "module not found" exception. I understand what this means: apparently I have (transitively) required a module that is not on the module path. But I have not required, used or otherwise that module, as far as I can infer.
I've inspected the module-info.java, and used jar --describe-module on all jars on the compiler's module-path and nowhere I can find that missing module even mentioned. So why does the compiler think it is missing?
If a simular situation would occur in Maven, I would dump the dependency tree and see where that dependency came from. And the java executable has a --show-module-resolution for doing this at runtime, but this does not work for the compiler.
Is there any way to get more information on why the compiler thinks a module is missing?