Sync'ing up jdk7 at b50

[Alan Bateman]

Andrew John Hughes wrote:
> :
> Sorry, I misremembered which build drop we synced against last.  It
> was actually b98, so my diffs will be a combination of the changes
> from b98->b99 and b99->OJ7-b50.
>   
No problem!
> :
> As I mentioned in a previous mail, we provide the option of NIO2
> support in the IcedTea6 and IcedTea7 repositories.  With bumping
> IcedTea7 to b50, I've been comparing what we have (b98) with what's in
> b50, and dropping most of our local copy in favour of the upstream b50
> version.  Once this work is complete, the version in 6 will also be
> bumped to the b50 version (which is trickier, as the version for 6
> moves to the classes to an alternate namespace to retain
> compatibility).
>   
Yes, this will be tricky (esp. the socket-channel area).


> :
> Interestingly, every file has changed in some
> way between b98 and the b50 OpenJDK7 drop, bar a few ancillary
> property and policy files in the test tree.
>   
In most cases it will be just the date range in the header. There isn't 
a lot of "code" changes.

> Are the changes between b99 and b50 in the NIO2 repository yet? Is
> there a public version of the change request that allowed it to go
> into the main 7 tree?
>   
I'll sync up the nio/nio forest later today. I meant to do that earlier 
this week but didn't get a chance.

I'm not sure I understand what you mean by "change request" here - do 
you mean the "changeset"? If so, here it is:
  http://hg.openjdk.java.net/jdk7/tl/jdk/rev/f06f30b29f36
Tim will have pushed that to jdk7/tl/jdk when pushing all bits for b50. 
If you mean the change requests (or bug IDs as we used to know them by) 
then they are in the change-set message.

-Alan.