8197532: Re-examine policy for the default set of modules when compiling or running code on the class path

[David Lloyd]

On Thu, Jul 19, 2018 at 10:03 AM Alan Bateman <Alan.Bateman at oracle.com> wrote:
>
> On 19/07/2018 15:14, David Lloyd wrote:
> > I've run into a problem with the change in java.se resolution.  There
> > is, from what I can tell, no way to add the java.se module to the
> > runtime that doesn't also break on Java 8.
> I think you need to explain what you are doing. JDK 8 doesn't know
> anything about modules or the "java.se" aggregator module. Is it
> possible that this is code that wants to fail if run on a run-time image
> that doesn't contain "java.se"?

When running on Java 9 or later, this code relies on being able to
reference java.se, and more importantly, all of the modules that it
includes, which worked OK on 9 and 10 but fails on 11.  When running
on Java 8, it uses the default parent class loader to load the
relevant classes and resources.

-- 
- DML