As part of the planned migration to git  it's been suggested that we combine some of the existing components into larger groups  so that it's more manageable in terms of checking out sources and tagging/branching .
Because 25 is a large number, and 1 is a small number, and we need some happy compromise.
Here's my proposal for how to divide the JBT 4.0 sources into 7 github repos (chunks), comprising 4 tiers of dependency. This is akin to the +0, +1, +2, +3 labels assigned to projects within the annual Eclipse release trains , used to define delivery times based on dependencies between projects.
I'm not thrilled with the names of the chunks, as something like "Central/Examples/Maven/Portlet" doesn't exactly roll off the tongue. If you have better names for the chunks, please suggest them.
But regardless of name, I think the above separation of concerns, and the implied build sequence workflow makes a lot of sense.
 http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#Milestones_and_Release_Candidates - "These delivery times are based on the dependencies between projects. They are labeled +0, +1, +2, and +3, with +0 coming first (the Platform) and +3 coming last (EPP). Projects themselves decide if they are +0, +1, +2, or +3."