On 03/03/2021 01:32, Thiago Henrique Hupner wrote:
When running some old applications in the module path, sometimes a jar
provides a service that doesn't exist in it.
So, the module system correctly informs about it, however, it doesn't
specify which module has this issue, so the way of debugging is testing
each jar individually with the --list-modules.
I think would be great if it was possible to change the exception in the
jdk.internal.module.ModulePath to show the module that has this problem.
Currently, the message is the following:
String msg = "Provider class " + cn + " not in module";
throw new InvalidModuleDescriptorException(msg);
Thanks, it should include the file path to the JAR file in the message
to make it easy to find the JAR file that can't be used as an automatic
module. I'll create an issue to track that.
-Alan
