Java 8 RFR 8020539: Clean up doclint problems in java.util package, part 2
dl at cs.oswego.edu
Thu Jul 18 11:36:27 UTC 2013
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.
> Essentially every file that can be found in Doug's CVS under src/main/util
> is destined for inclusion in openjdk.
> 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.
More information about the core-libs-dev