Fix "module not found" error when using -J--release=11 option

[aserkes]

Fix "module not found" error when using -J--release=11 option

[lukasj]

this is not the best way to resolve the problem. Consider this:

I have a project and one dependency is a module while the other is not. My module-info defines requires some-module; and javac command I would use in this case would look like javac --module-path some-module.jar --class-path otherlib.jar ... Now, if my project has a @WebService then running wsgen is going to fail because the otherlib.jar is not required by my project.

What I think would be better to:

• add an option to fallback to existing behaviour (ie just use classpath for everything), option name on the command line could be ie -Xno-modules
• by default put all required direct wsgen dependencies (except of ha-api for now) on the module path and the rest on the classpath
• define new -modulepath option for wsgen tool itself (similar to existing -classpath)
• pass the value of the new -modulepath option + all required direct wsgen dependencies (except of ha-api for now) to javac invocation as --module-path
• pass the value of current -classpath + remaining dependencies to javac invocation as --class-path

adopt this change in the mvn plugin as needed

(or the first option could be -Xuse-modules to turn on the new behaviour ... which is probably better)