Per-component repositories

[Brad Wetmore]

> For instance, as a developer in Core Libraries, it would seem that I only need
> to retrieve the "jdk" portion of the repository since that's where the
> implementation of those classes resides. However, I would need to be pretty
> confident to not do a full build of the entire forest before I did my commit.

I would like to offer the following guidance.

If you're changing the layout of any part of the JDK, you really should 
do a full build on the whole repository, at least including images 
(generally as the last step before integrating).  Yes, the file may have 
compiled correctly, but then something such as the images target broke, 
or the file wasn't included in the final rt.jar.  There's a lot more 
than javac to be concerned with when you're moving target files around. 
  Gatekeepers don't particularly enjoy last minute images target 
breakage.  ;)

> Yes, from the Guide, "Terminology and Naming Scheme":
> 
>   The OpenJDK repository forests are located at http://hg.openjdk.java.net/.

There was talk that the output might be tweaked into logical chunks, and 
not alphabetical.  I don't think it's in the immediate plans, but still 
would be nice.

i.e.

jdk7/2d
jdk7/2d/corba
jdk7/2d/hotspot
jdk7/2d/jaxp
jdk7/2d/jaxws
jdk7/2d/jdk
jdk7/2d/langtools

jdk7/2d-gate
jdk7/2d-gate/corba
jdk7/2d-gate/hotspot
jdk7/2d-gate/jaxp
jdk7/2d-gate/jaxws
jdk7/2d-gate/jdk
jdk7/2d-gate/langtools

> - MASTER
...deleted...
>   - tl
>     - jsn

At least for JSN, that is correct.  JSN is a "child" of TL because our 
code tends to be very interconnected, and having separate integration 
slots proved to be dangerous.

Brad