Return-Path: Mailing-List: contact user-help@ant.apache.org; run by ezmlm Delivered-To: mailing list user@ant.apache.org Received: (qmail 46771 invoked from network); 7 Mar 2003 10:45:28 -0000 Received: from mail-gw.imt.im.se (195.100.17.67) by daedalus.apache.org with SMTP; 7 Mar 2003 10:45:28 -0000 Received: from fsecsth3 (fsecsth3.im.se [193.14.16.251]) by mail-gw.imt.im.se (8.9.3/8.9.3) with SMTP id LAA188884 for ; Fri, 7 Mar 2003 11:44:47 +0100 Received: from [193.14.16.192]:3933 (EHLO msxsth3.im.se) by fsecsth3.im.se ([193.14.16.251]:25) (F-Secure Anti-Virus for Internet Mail 6.0.34 Release) with SMTP; Fri, 7 Mar 2003 10:36:34 -0000 Received: by msxsth3.im.se with Internet Mail Service (5.5.2653.19) id ; Fri, 7 Mar 2003 11:46:16 +0100 Message-ID: <6C765F018BE36B4989905B52870AF26603ACD8DC@msxsth3.im.se> From: Rosendahl Sten - stro To: "'Ant Users List'" Subject: RE: AW: AW: AW: anthill vs. cruisecontrol Date: Fri, 7 Mar 2003 11:46:11 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2E496.C4ABDCA0" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C2E496.C4ABDCA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Read about dependency groups in the AntHill manual (http://www.urbancode.com/projects/anthill/manual/anthillusermanual.pdf)= . -----Original Message----- From: mmay@gmx.net [mailto:mmay@gmx.net] Sent: Friday, March 07, 2003 11:40 AM To: Ant Users List Subject: Re: AW: AW: AW: anthill vs. cruisecontrol Okay, understood this now. But can AntHill handle project dependencies? = E.g. I am building SubProject B, and AntHill recognizes, that B is dependent = on A, so A is build as well? > CC can=B4t control project dependencies. So that is an idea for a > workround: > > SubProject > | > +-- dist > | sub.jar <--- contains all you need to use SubProject > +-- src > > If the build is successful copy SubProject/dist/sub.jar to > Project/lib/sub.jar. This is a kind of notification. > > > > Project > | > +-- dist > +-- lib <--- external libs this project requires > | sub.jar <--- copied from SubProject/dist > +-- src > > So sub.jar is IN the filelist CC evaluates. And if it changed CC will > do a > rebuild. > > > > > Jan Mat=E8rne > > > > > -----Urspr=FCngliche Nachricht----- > > Von: mmay@gmx.net [mailto:mmay@gmx.net] > > Gesendet am: Freitag, 7. M=E4rz 2003 11:29 > > An: Ant Users List > > Betreff: Re: AW: AW: anthill vs. cruisecontrol > > > > I don't think that I understood you right. I should put all > > projects in our > > Version Control System Root directory and also put the Jars in = there? > > BTW, we are using VSS :-(, and because we are going to use > > Branching as well > > it is not feasable to use the Root as a space to store files > > (due to the > > Branching mechanism of VSS, which seems very strange to mee). > > > > > > > > > ASAIK CC doesn=B4t support project dependencies (directly). Gump = is > > > the tool for project dependencies (if I remind that chapter in > > > Eriks book right :-). > > > > > > But maybe that could work: > > > put the distribution of the subprojects in the cvs of the > > main project. > > > So CC should notice the modification in subprojects and do > > a rebuild. > > > > > > Because that will produce lot of cvs space (many many libs > > ...), maybe > > > you can write a simple textfile. (main thing it should be a > > file with > > > modification date). And the Ant buildfile evaluates that > > and gets the > > > actual binary. > > > > > > > > > > > > Jan Mat=E8rne > > > > > > > > > > -----Urspr=FCngliche Nachricht----- > > > > Von: mmay@gmx.net [mailto:mmay@gmx.net] > > > > Gesendet am: Freitag, 7. M=E4rz 2003 10:03 > > > > An: Ant Users List > > > > Betreff: Re: AW: anthill vs. cruisecontrol > > > > > > > > Hello, > > > > we have a project, where we have many sub-projects. This > > > > means, all the > > > > sub-projects are basically their own projects and the only > > > > common thing is, that > > > > they share a common include_build.xml. Anyway, these > > > > sub-projects depend on > > > > each other. > > > > Can this be done by CruiseControl or AntHill OS? I did not > > > > found anything > > > > useful on the page of CruiseControl and neither on the > > > > AntHill OS page. > > > > > > > > Regards > > > > > > > > Markus > > > > > > > > > > who of you is doing continues integration? > > > > > > > > > > We are doing it more or less - based on personal > > > > preference. Personally, > > > > > I like to integrate several times a day; sometimes > > several times an > > > > > hour. > > > > > > > > > > > where are the > > > > > > limits of it? e.g a build takes 30 minutes, so makes it = sense > > > > > > > to integrate every time someone (of maybe 30 developers) > > > > > > checks something in. wouldnt that cause that every 30 = minutes > > > > > > > a build runs and everyone gets a e-mail (failed/ok), thats > > > > > > makes him bored about the buildmails... or is it possible = to > > > > > > just inform the developer thats class made the build fail? > > > > > > > > > > Cruise Control (Anthill too, I suppose) only informs those > > > > developers > > > > > who changed something since the last successfull build. And > > > > certainly > > > > > all those *need* to be informed. In fact, I don't feel good > > > > when I don't > > > > > get the cruise control email telling me that everything > > > > still works fine > > > > > a short time after check-in. > > > > > > > > > > In my experience, the only limit is build time - it needs > > > > to be short. > > > > > In fact, the more developers are working on a project, the > > > > shorter it > > > > > needs to be (to reduce conflicts). So you need to partition > > > > big projects > > > > > - well, you need to do this anyway... > > > > > > > > > > Did that help? > > > > > > > > > > Ilja > > > > > > > > > > > > > > > -- > > > > > ++ disy auf der CeBIT: Besuchen Sie uns vom 12. - 19. M=E4rz > 2003 > > > in > > > > > Hannover im SUN-Partnerpavillon in Halle 1, Stand 8a1 ++ > > > > > ++ disy Cadenza: Informationsintegration am i*net > > Arbeitsplatz ++ > > > > > ++ disy Conference: The easy way of audio conferencing ++ = disy > > > > > ++ Call-Back Office: Call-Back-Buttons f=FCr > > > > Kundenservice im Web > > > > > ++ > > > > > > > > > > Ilja Preu=DF =20 > preuss@disy.net > > > > > disy Informationssysteme GmbH =20 > > > http://www.disy.net > > > > > Stephanienstr. 30 Tel: +49 > > > > 721 1 600 624 > > > > > D-76133 Karlsruhe, Germany Fax: +49 > > > > 721 1 600 605 > > > > > > > > > > ++ Weitere Informationen finden Sie unter > http://www.disy.net ++ > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For > > > > additional commands, e-mail: user-help@ant.apache.org > > > > > > > > > > -- > > > +++ GMX - Mail, Messaging & more http://www.gmx.net +++ > > > Bitte l=E4cheln! Fotogalerie online mit GMX ohne eigene Homepage! > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For > > > additional commands, e-mail: user-help@ant.apache.org > > > > > > > -- > +++ GMX - Mail, Messaging & more http://www.gmx.net +++ > Bitte l=E4cheln! Fotogalerie online mit GMX ohne eigene Homepage! > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org > For additional commands, e-mail: user-help@ant.apache.org > -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte l=E4cheln! Fotogalerie online mit GMX ohne eigene Homepage! --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org ------_=_NextPart_001_01C2E496.C4ABDCA0--