Compilation (still) depends on order of imports

[Jan Lahoda]

Hi Liam,

Thanks for the report. I am afraid I was not able to reproduce. I tried on:
$ javac -fullversion
javac full version "1.9.0-ea-b54"

and on a custom build from jdk9/dev/langtools, tip:
$ hg tip
changeset:   2850:32a2e7249884
tag:         tip
parent:      2849:75cedc6db8c2
parent:      2848:f5a1cb1309ae
user:        lana
date:        Thu Mar 12 21:13:42 2015 -0700
summary:     Merge

Is there something special I need to do? Could you please try on JDK 9 b54?

Thanks,
     Jan

On 15.3.2015 23:00, Liam Miller-Cushon wrote:
> I think I found a bug related to JEP 216. With javac9-dev @ r2850, the
> following program fails to compile unless the order of imports is reversed.
>
> It looks like the current implementation isn't lazy enough to handle the
> dependency between the two on-demand imports if 'I' is inherited into
> 'C'. If 'I' is declared directly in 'C' then it works.
>
> {{{
> package P;
>
> import static P.Outer.Nested.*;
> import static P.Q.C.*;
>
> public class Outer {
>    public static class Nested implements I {
>    }
> }
>
> package P.Q;
>
> public class C extends D {
> }
>
> package P.Q;
>
> public class D {
>    public interface I {
>    }
> }
> }}}
>
> $ javac P/Outer.java P/Q/D.java P/Q/C.java
> P/Outer.java:7: error: cannot find symbol
>    public static class Nested implements I {
>                                          ^
>    symbol:   class I
>    location: class Outer
> 1 error