WARNING when a module tries to export to another module but the other module is not yet compiled

[Alex Buckley]

This list is not able to help with Maven configuration issues.

However, it's actually allowed for module x to say `exports foo to y;` 
when module y doesn't exist.

(JLS 7.7.2: "It is permitted for the to clause of an exports or opens 
directive to specify a module which is not observable (§7.7.6).")

Alex

On 10/18/2023 4:36 PM, Siddharth Jain wrote:
> I am using JPMS with Maven compiler plugin. say i have:
> 
> module x {
> exports foo to y
> }
> 
> when i do a clean install I get a WARNING from maven that y does not 
> exist. Its true, the dependency tree has to be built from bottom to top 
> so x will be built first and only then y can be built.
> 
> i also see strange errors while executing tests where maven clean 
> install will fail with some errors saying type X could not be found but 
> if i re-run the command it passes.
> 
> i think this error happens because at first y does not exist so JPMS 
> does not know about it. but when i re-run y does exist. is that right?
> 
> i don't mind the WARNING my question is about the weird errors. has 
> anyone run into same issue?