Thanks for the pointer Max, but I think I managed to figure out what my new
problem was and to find a solution for it.
In my current dev setup, I'm running IntelliJ on Windows connected to a
Samba network share which holds my jdk9 clone, which itself is hosted on an
Ubuntu VM on my local machine (
Looks good.
Mandy
> On Sep 13, 2016, at 2:41 AM, Sundararajan Athijegannathan
> wrote:
>
> Modified existing test to check quotes around properties added by jlink:
>
> Updated webrevs:
>
> jdk:
>
> http://cr.openjdk.java.net/~sundar/8163320/jdk/webrev.02/
>
> Top:
>
> http://cr.openjdk.ja
Hello,
I've updated the patch to the current situation. The top-level
repository patch is here:
http://cr.openjdk.java.net/~jlahoda/8153362/top-level.03/
Langtools repository patch is here:
http://cr.openjdk.java.net/~jlahoda/8153362/langtools.04-phase2/
Does this look OK?
Thanks,
Jan
O
When the buildjdk logic was added to the jdk9 build system, it did not
completely
cover the use cases required in the mobile/dev builds. We have been
working around
this issue using a prebuilt macosx buildjdk with the --with-build-jdk
autoconf option.
This is an awkward workaround, because the b
Modified existing test to check quotes around properties added by jlink:
Updated webrevs:
jdk:
http://cr.openjdk.java.net/~sundar/8163320/jdk/webrev.02/
Top:
http://cr.openjdk.java.net/~sundar/8163320/top/webrev.02/
Thanks
-Sundar
On 9/9/2016 9:07 PM, Mandy Chung wrote:
> Looks good.
>
> I