On 07/17/13 21:03, Martin Buchholz wrote:
I'm surprised no one has explained. The jsr166 project is upstream of openjdk and is primarily maintained by Doug Lea. http://gee.cs.oswego.edu/dl/concurrency-interest/index.html Essentially every file that can be found in Doug's CVS under src/main/util is destined for inclusion in openjdk. http://gee.cs.oswego.edu/cgi-bin/viewcvs.cgi/jsr166/src/main/java/util/ If modifications are made to openjdk directly, they are at risk of being overwritten in the next sync.
To further explain: jsr166 initially introduced in JDK5, java.util.concurrent, plus a few things in java.util and elsewhere. These sources are also used in Android, and ongoing maintenance and extension include participation of folks from Google. Until legal matters surrounding this are straightened out, to be cautious, we always commit first into jsr166 repository and then sync. We do happily accept patch requests though, and try to keep all parties content. While there is no rule saying that Oracle engineers must go through this pathway for updates to any files originating from jsr166<n>, it has worked pretty well, considering all the alternatives. -Doug
