Can't run Graal with JDK 11

[Doug Simon]

> On 2 May 2018, at 11:08, Andrew Haley <aph at redhat.com> wrote:
> 
> On 05/02/2018 09:55 AM, Doug Simon wrote:
> 
>> Until that's done, I agree that getting work done on jaotc will be
>> challenging. The only workaround I can think of is to use the `mx
>> updategraalinopenjdk` command as part of your workflow.
> 
> That sounds like it would probably work, but of course it corrupts the
> source of the OpenJDK I'm working on.

The updategraalinopenjdk tool should only touch the Graal directories in OpenJDK. If not, it's a bug and will be fixed.

>  I guess I can live with that
> for now, but as Graal is part of OpenJDK and seems likely to be
> important we're going to have to make it easier for people to work on.
> In the long run, as you might expect, I'd prefer it to be a
> first-class part of OpenJDK.

Yes, I agree that would simplify the OpenJDK development process. However, Graal is used in a number of other contexts and as such needs to be developed and tested independently of OpenJDK. We will continue to try mitigate OpenJDK development pain by providing tools such as updategraalinopenjdk.

-Doug

> 
> -- 
> Andrew Haley
> Java Platform Lead Engineer
> Red Hat UK Ltd. <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com&d=DwICaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=BmNY5KuefACTr_P43s8fXOXgNDkDiqlviyafeiVaP18&m=4Ta6hVPN5Qu7cG-YTF91AIT5pZ4RGSglChs4IHLKYwc&s=chjg_vYX6K17Z99pKE4bVsou80Qi4ldWxGhQTBL2n8A&e=>
> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671