You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a multi-project setup, root project usually does not have /src/main/java directory - the sources are in the subprojects. However, the new module name detector fails, if it does not find module-info.java descriptor.
There is a workaround for that:
javaModule.name =''
It is a bit ugly. Generally, if there is no directory with the sources, we should skip parsing module-info.java at all.
The text was updated successfully, but these errors were encountered:
You could also mix module-enabled projects and non-module-enabled projects (auto-modules).
So you should probably not depend on whether the source directory is present, but whether there is a module-info.java?
And also there could be multiple source sets, so you shouldn't only pimp the main source set, but also the other source sets?
In a multi-project setup, root project usually does not have
/src/main/java
directory - the sources are in the subprojects. However, the new module name detector fails, if it does not findmodule-info.java
descriptor.There is a workaround for that:
It is a bit ugly. Generally, if there is no directory with the sources, we should skip parsing
module-info.java
at all.The text was updated successfully, but these errors were encountered: