Source code mapping to projects

[Jonathan Gibbons]

On 05/04/2012 07:21 AM, 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?
>
> Cheers,
> Martijn

It's long been a never-quite-high-enough-priority wishlist item to have 
a utility that you could give a class name to and have it return an 
owner in some form, preferably one that is easily mapped to an email 
address. Not only would this be useful for what you are asking for here, 
it would also be useful for (semi-)automatically directing messages 
reporting test failures and so on.

-- Jon