I'm sure its more complicated than this, but ... At one [high] level, it would seem that the scm plugin could check out the parent directory [only], and then check out the sub-directories corresponding to the aggregated sub-projects as described in the parent project's pom.
And then proceed with the build lifecycle as usual. Brad > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 17, 2008 8:25 PM > To: [email protected] > Subject: Re: CI Builds Need Only a Fraction of the > Sub-Projects in the SCM Repo > > We're looking to propose something for a future version to > improve this behaviour. > > At the moment, you have another alternative in that you can > use the checkbox on addition that runs the build as one > checkout instead of separate modules. > > HTH, > Brett > > On 18/04/2008, Harper, Brad <[EMAIL PROTECTED]> wrote: > > Continuum is set to build a maven project aggregating > several <module> > > sub-projects. In reality, the directory containing this top-level > > project contains *many* more sub-projects than it's pom.xml > describes. > > > > When continuum build runs, it checks out the entire tree > beneath this > > main project, including all of the sub-directories > associated with the > > sub-projects that aren't specified in the pom. The activity > checks out > > far too much from the SCM repository than is necessary for the CI > > build itself [as defined by the pom hierarchy] and adds tens of > > minutes to the overall CI build time. > > > > Suggestions on how to better control the behavior of the > SCM checkout > > performed by the continuum build? Thanks. > > > > > > Brad > > > > > -- > Brett Porter > Blog: http://blogs.exist.com/bporter/ >
