On Mon, Mar 17, 2008 at 12:24 PM, Simon Nash <[EMAIL PROTECTED]> wrote:
> ant elder wrote:
> > On Sun, Mar 16, 2008 at 7:20 AM, ant elder <[EMAIL PROTECTED]> wrote:
> >
> >>
> >> On Sat, Mar 15, 2008 at 10:41 PM, Simon Nash <[EMAIL PROTECTED]> wrote:
> >>
> >>> The default mvn build takes a long t
ant elder wrote:
On Sat, Mar 15, 2008 at 10:41 PM, Simon Nash <[EMAIL PROTECTED]> wrote:
The default mvn build takes a long time to run and consumes
a large amount of disk space. As we add more modules and tests
to the default build, the time and space requirements continue
to increase.
IMO w
ant elder wrote:
On Sun, Mar 16, 2008 at 7:20 AM, ant elder <[EMAIL PROTECTED]> wrote:
On Sat, Mar 15, 2008 at 10:41 PM, Simon Nash <[EMAIL PROTECTED]> wrote:
The default mvn build takes a long time to run and consumes
a large amount of disk space. As we add more modules and tests
to the de
On Sun, Mar 16, 2008 at 7:20 AM, ant elder <[EMAIL PROTECTED]> wrote:
>
>
> On Sat, Mar 15, 2008 at 10:41 PM, Simon Nash <[EMAIL PROTECTED]> wrote:
>
> > The default mvn build takes a long time to run and consumes
> > a large amount of disk space. As we add more modules and tests
> > to the defau
On Sat, Mar 15, 2008 at 10:41 PM, Simon Nash <[EMAIL PROTECTED]> wrote:
> The default mvn build takes a long time to run and consumes
> a large amount of disk space. As we add more modules and tests
> to the default build, the time and space requirements continue
> to increase.
>
> IMO we need to
The default mvn build takes a long time to run and consumes
a large amount of disk space. As we add more modules and tests
to the default build, the time and space requirements continue
to increase.
IMO we need to either significantly reduce the time and space
requirements of the default build,
