I see now that the original change applied to classpath mode. I'm
going to go have some caffeine now, thanks.
On Thu, Jul 12, 2018 at 9:43 AM David Lloyd wrote:
>
> I guess this was a result of:
>
> > The webrev with the proposed changes is here:
> >http://cr.openjdk.java.net/~alanb/8197532/w
I guess this was a result of:
> The webrev with the proposed changes is here:
>http://cr.openjdk.java.net/~alanb/8197532/webrev/
>
> The CSR for the change is linked from the bug. The only behavioral
> impact is that the "java.se" aggregator module is not resolved resolved
> (at least not unle
It does work if you manually add "java.se" to the command line via
"--add-modules" though. Was this an intentional change?
On Thu, Jul 12, 2018 at 9:37 AM David Lloyd wrote:
>
> In the most recent EA, calling
> ModuleLayer.boot().findModule("java.se") now appears to return an
> empty Optional, wh
In the most recent EA, calling
ModuleLayer.boot().findModule("java.se") now appears to return an
empty Optional, which is a change in behavior compared to 9/10 AFAICT.
However the module does appear in the output of "java --list-modules".
--
- DML
