Source code mapping to projects
Alan.Bateman at oracle.com
Fri May 4 14:58:42 UTC 2012
On 04/05/2012 15:21, Martijn Verburg wrote:
> Hi all,
> As part of the plan to pre-review low hanging fruit for the OpenJDK
> (such as coinification, javac warnings and the like). One of the
> challenges is to split the patches into the appropriate groups (2d,
> core-lib etc) and then a per class basis for easy review.
> Is there a rough mapping outlined of OpenJDK source code to groups?
Most of the group pages (http://openjdk.java.net/groups/<group>) have a
list of APIs and/or source directories for the group. However for the
refactoring changes that you are talking about, warnings, coinification,
etc. then slicing and dicing to that level of granularity should not be
needed; the code review and sponsorship overhead will be more than the
actual work. That said, the core and client changes have different
integration forests and it does make things a bit easier (integrators
doing merging in particular) if you can do a very coarse grain split
into core and client. When I say client then I mean AWT, 2D, Swing and
related areas. When I say "core" I mostly mean headless (libraries,
security, networking, ..). In recent times this relatively coarse grain
split has worked well.
More information about the discuss