Return-Path: Delivered-To: apmail-incubator-river-dev-archive@minotaur.apache.org Received: (qmail 63831 invoked from network); 14 Jan 2011 11:48:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Jan 2011 11:48:31 -0000 Received: (qmail 87173 invoked by uid 500); 14 Jan 2011 11:48:31 -0000 Delivered-To: apmail-incubator-river-dev-archive@incubator.apache.org Received: (qmail 87098 invoked by uid 500); 14 Jan 2011 11:48:30 -0000 Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: river-dev@incubator.apache.org Delivered-To: mailing list river-dev@incubator.apache.org Received: (qmail 87090 invoked by uid 99); 14 Jan 2011 11:48:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Jan 2011 11:48:29 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [61.9.168.140] (HELO nskntmtas02p.mx.bigpond.com) (61.9.168.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Jan 2011 11:48:20 +0000 Received: from nskntotgx01p.mx.bigpond.com ([61.9.223.241]) by nskntmtas02p.mx.bigpond.com with ESMTP id <20110114114755.DJBT3622.nskntmtas02p.mx.bigpond.com@nskntotgx01p.mx.bigpond.com> for ; Fri, 14 Jan 2011 11:47:55 +0000 Received: from [10.1.1.2] (really [61.9.223.241]) by nskntotgx01p.mx.bigpond.com with ESMTP id <20110114114755.DOTC25056.nskntotgx01p.mx.bigpond.com@[10.1.1.2]> for ; Fri, 14 Jan 2011 11:47:55 +0000 Message-ID: <4D303677.4000308@zeus.net.au> Date: Fri, 14 Jan 2011 21:41:43 +1000 From: Peter Firmstone User-Agent: Thunderbird 2.0.0.14 (X11/20080531) MIME-Version: 1.0 To: river-dev@incubator.apache.org Subject: Re: build mechanisms References: <4D2EDFE3.8000307@qcg.nl> <4D300E33.5080408@qcg.nl> <4D301D42.5000601@zeus.net.au> <4D30255F.3070006@qcg.nl> <4D302EAA.7020406@qcg.nl> <4D3032E0.4050109@zeus.net.au> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150201.4D3037EB.00A8,ss=1,fgs=0 X-Virus-Checked: Checked by ClamAV on apache.org Tom Hobbs wrote: >> Well one problem with the current build system is the time taken, not only >> to build it, but to test it, taking around 20 hours. A modular build will >> speed development, allowing developers to concentrate on one module and the >> tests applicable to that module. >> > > Don't we get around this by only specifying certain test categories or > even individual tests? Would better documentation/examples on how to > do that solve the problem equally well? > > When building on Hudson, isn't one 20 hour build the same thing a 20 > one hour module builds? > > What did I miss? > > I'm not trying to rubbish all the effort that has gone into the Maven > build (and that other one the name of which escapes me). I do > apologise if it looks that way. I'm just trying to understand. > There are many reasons other than shortened build and test times, these will become evident later, for now the modular build is in skunk, I encourage people to have a look and get involved as it progresses. Cheers, Peter.