That's a possibility indeed, but the disk space issue is by far less
important than the ability to build an individual subproject on demand
from continuum!
Ideally, continuum should be aware of the project/modules structure
and use the module subdirectory checked out with the parent as its
working directory, and not create a separate one.
-Olivier
Wendy Smoak wrote:
On 6/13/07, Olivier Dehon <[EMAIL PROTECTED]> wrote:
I used to use the 2nd layout you describe because it made sense as the
continuous integration engine that I use (continuum) checks out every
project in separate subdirectories for each subproject.
That way it didn't checkout all the subprojects alongside the parent
POM just to build the parent...
I later had to change that layout and take the diskspace hit of moving
to the 1st layout you describe, because the release plugin will not
work otherwise.
This might help to get the disk space back: remove the
--non-recursive switch from the build definition on the parent, and
delete all the separate child modules. (That should be an option when
you add a project...)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
