Closed hrstoyanov closed 7 months ago
Hi. The plugin is always looking at all Jars on the class/module path, as the main objective is to help users to get to a clean Java Modules setup. By default, it is configured to fail for Jars that do not even have a Module Name.
You can turn off the fail behavior via:
extraJavaModuleInfo {
failOnMissingModuleInfo = false
}
I added this to my conventions:
with the intention to modularize this jar:
However, I am getting an erro with an unrelated jar I did not have problems with . Why??? Note that issue immediately starts only by including the plugin!