From ivy-user-return-780-apmail-incubator-ivy-user-archive=incubator.apache.org@incubator.apache.org Thu May 03 10:25:25 2007 Return-Path: Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org Received: (qmail 82679 invoked from network); 3 May 2007 10:25:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 May 2007 10:25:25 -0000 Received: (qmail 90554 invoked by uid 500); 3 May 2007 10:25:31 -0000 Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org Received: (qmail 90524 invoked by uid 500); 3 May 2007 10:25:31 -0000 Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@incubator.apache.org Delivered-To: mailing list ivy-user@incubator.apache.org Received: (qmail 90514 invoked by uid 99); 3 May 2007 10:25:30 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2007 03:25:30 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of gscokart@gmail.com designates 66.249.92.169 as permitted sender) Received: from [66.249.92.169] (HELO ug-out-1314.google.com) (66.249.92.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2007 03:25:21 -0700 Received: by ug-out-1314.google.com with SMTP id y2so410392uge for ; Thu, 03 May 2007 03:24:59 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:in-reply-to:x-mimeole:thread-index; b=XLvFjV59LAiacqiqcn9Ipq1VHw6+S/aWRHvqDpoyk58OzSGJClCrvT57P/74KAAQwkFLQMrYLqtIAkwA10odtJBPCqfYkfUW2wSgXW/OFEG8PAEm1r55pHiew855DsjU6GLmjAUgoZ0jtnj0IjwRpvdhV1mN1atiinj39zRLy9w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:in-reply-to:x-mimeole:thread-index; b=ZzMr+LihcydvjWG6Fns7VepAFm2b4fDXF9hpeBNdWZ5zPypg9YiZSd/tiM4wTKGbAVL2qOppTAGzUF4kvL6ugRXXdmn2s7M+TrDXX2vAemE4O8QxwD8zrQZJKKk88VCx3xLoiXohUjG4EA04gw3axKA9MMzAIoao+xj8Xa+31/4= Received: by 10.67.30.6 with SMTP id h6mr1809911ugj.1178187899554; Thu, 03 May 2007 03:24:59 -0700 (PDT) Received: from SCOKARTGXP ( [195.122.110.8]) by mx.google.com with ESMTP id y7sm1389386ugc.2007.05.03.03.24.56; Thu, 03 May 2007 03:24:56 -0700 (PDT) From: "Gilles Scokart" To: Subject: RE: IvyCruise replacement Date: Thu, 3 May 2007 12:25:45 +0200 Message-ID: <006a01c78d6d$695f3f70$2120a8c0@isabelteam.be> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <4639AD11.4090603@red56.co.uk> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: AceNax4jlgWLVAAhTAOGOJAQTdnbDQAAUlSQ X-Virus-Checked: Checked by ClamAV on apache.org Seems to be a good start. You will have your modules able to rebuild when one of its dependency has changed. But you might have a few things to consider: 1. How to clean your local repository if required. 2. You might have some modules rebuild too often. For example if you have 3 modules A ,B and C. B depends on A. C depends on A and B. When A is rebuild, it should be better to wait that B is rebuild before rebuilding C. For the first point, having enough disk space, combined with an occasional clean and full rebuild might be a solution. For the second point (if you consider it is a problem), you might take some inspiration from the new veto modificationset. Gilles > -----Original Message----- > From: Tim Diggins [mailto:tim@red56.co.uk] > Sent: jeudi 3 mai 2007 11:36 > To: ivy-user@incubator.apache.org > Subject: Re: IvyCruise replacement > > have been thinking about this and am wondering if the simplest thing > would actually be to make an ivy-wrapper around the modificationset - so > that ivy swallows all the modificationsets, and checks all the > (--local--) dependencies' modificationsets, and if there are any > modificationsets on those, then it returns a false - ie. there will only > a modificationset on a project once all of its dependencies have cleared > their modificationsets. > > what do you think? > > -- Tim > > > Tim Diggins wrote: > > Hi - > > I'm considering ivy as a mechanism to express and manage dependencies > > (currently only expressed in ant tasks), but as one of my main drivers > > is to fix my continuous-build problems, am wondering what people do > > who use ivy and cruisecontrol at present, given that ivycruise is > > apparently not active and not working with latest cruisecontrol? > > > > What do people do? > > * not use cruisecontrol? > > * live with the failures when things get built in the wrong order? > > * Use some other kind of modificationset and just update all > > dependencies each build? > > > > any perspectives helpful > > ] > > thanks > > > > Tim > > > > > > -- > > --------------- > Tim Diggins > http://www.red56.co.uk/people/tim