When I import java 11 maven project with modules to latest versions of Eclipse I got a whole bunch of hardly visible error, that seems to be whole inconsistency. Indeed when opening in Intellij IDEA or NetBeans it does imports correctly. The first ample error is "The project was not built since its build path is incomplete" - "Cannot find the class file for java.lang.Object. Fix the build path then try building this project." This error appears in two child modules. (This project is docker-based, multimoduled although import of another simple module-infos project also cannot be imported correctly in Eclipse). Next 2 errors are produced in two classes of aforementioned maven modules: " The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files. "
Manipulation with adding JDK 11 to submodules buildpath just leads to the thousands of problems. Such big bunch of errors also appears when I use Eclipse-File-Maven-Update. Moreover when I try to edit most of existing classes or add new ones I got red underline that tells
"Implicit super constructor Object() is undefined for default
constructor. Must define an explicit constructor"
So almost no opportunity to use Eclipse in this case. But I noted that such issue is produced just when project uses modules (module-info files introduced in java9). When I import project on jdk 8 (even not installed on system), or even on jdk11 without module-info files, all is fine in Eclipse after import. One visible settings difference in Eclipse is that of when I use old no-module project the Build Path is composed with jre environment 8 and maven dependency items, but when using "module-info" project the Build path contains -module path, and -classpath. So I even do not know where to add jre 11, indeed adding does not resolve issue, just make more errors. So what is the resolution of the case??? What settings to do in Eclipse? Maybe override some project files that maybe inherently created in Intellij IDEA.