Initial webrev with changes for JDK 9

[Alan Bateman]

I've refreshed the webrevs here:
     http://cr.openjdk.java.net/~alanb/8142968/3

so that we have an up to date snapshot of what is currently in the 
jigsaw/jake forest. The webrevs are against jdk-9+110.

Thank you to the many people that have been helping with the review and 
addressing comments/issues quickly. Overall, I think we are converging 
to the bits that we will push to jdk9/jdk9. As expected, there are a few 
issues where some re-work is needed and those issues will be tracked in 
JIRA to avoid destabilizing things now.

So at this point then I think we are on track to integrate into JDK 9 
next week for jdk-9+111. If something serious comes up then we might 
have to change that plan and go for the week after that, I hope not. I 
sent a note to jdk9-dev last week [1] so that the wider project knows 
what is coming. I will send another note later in the week once 
confidence is higher about next week.

In terms of logistics then we have created jigsaw/m3 as a staging 
forest. We used jigsaw/m1 to stage JEP 201 and jigsaw/m2 to stage JEP 
220 so this is a similar deal except jigsaw/m3 has jcheck configured to 
only accept change-sets that can be pushed to JDK 9. There will be 
activity in this new staging forest for the next few weeks, the 
notifications go to this mailing list so apologies for the spam.

-Alan.

[1] http://mail.openjdk.java.net/pipermail/jdk9-dev/2016-March/003877.html