Doing a full build with a flattened tree

["Brian E. Fox" <br...@reply.infinity.nu>]

Hello again,
 
For the purposes of testing, verification and official deployment, I
think we need the ability to build our full product rather easily. We
are thinking about the following structure on svn:
 
/modules/moduleA/trunk/modulea
/modules/moduleA/branches/brancha-1
/modules/moduleA/tags/release1
...
/modules/moduleZ/trunk/moduleZ
/modules/moduleZ/branches/branchZ-1
/modules/moduleZ/tags/release1
 
/projects/project1/trunk/project1
/projects/project1/branches/project1-1
/projects/project1/tags/release1.0
...
 
Project 1 may consist of moduleA,moduleC and moduleD
Project 2 may consist of moduleA,and moduleF
 
The idea is that a project tree should contain the things that produce a
final deliverable of all the modules grouped together...such as the
war/Ear and or assemblies. 
 
If I setup a project with the type of POM and define the modules like
the following example, it would go build everything: (using project1
above as an example)
  <packaging>pom</packaging>
   <modules>
       <module>../../../../modules/moduleA</module>
       <module>../../../../modules/moduleC</module>
       <module>../../../../modules/moduleD</module>
   </modules>
 
 
Here's the problem:
Getting all the source onto the build machine will be kindof
complicated. We can't just checkout /modules because that will get all
tags and branches in addition to the trunk. We'd need to checkout each
branch/tag by itself for each module in a project.
 
Is there a good solution to this within m2 that would allow a download
of the source from svn and then build it as it iterates through the
modules? Is there a better way to do this?
 
Thanks.