Eclipse appears to get confused when combining native JS modules with "fully export Maven dependencies" #1894
Description
This is a weird one and I'm not sure it'll reproduce easily. You can see my project setup, minus the JS module, here. I have a few native Java modules that import some stuff from Maven. I'm using Spring Boot via a bunch of spring-boot-starter Maven imports, so I have to use the "fully export Maven dependencies" option in order for the code to compile. Everything worked fine until I added a native JavaScript module that wants to import ceylon.interop.browser, another native JS module.
When Eclipse tries to compile this set of modules, it looks like it gets confused about who is importing what, because one of the Java modules gets this error: "Pre-resolving of module failed: Could not find module: ceylon.interop.browser/1.3.3" and the compilation aborts. The ceylon compile command-line tool appears to work fine. If I take away the "fully export Maven dependencies" option, the error about ceylon.interop.browser goes away, but the rest of the code no longer compiles, because of all the missing Spring Boot stuff.
This also happens when my native JS module imports herd.thrillon/1.0.1, which is the only other JS-only module I can find in the Herd. This does not happen when the module imports a module that has also been compiled for the JVM.
I can try to boil all this down to a more focused test case, if necessary.