Return-Path: Delivered-To: apmail-ant-user-archive@www.apache.org Received: (qmail 22278 invoked from network); 21 Apr 2004 07:59:31 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 21 Apr 2004 07:59:31 -0000 Received: (qmail 53193 invoked by uid 500); 21 Apr 2004 07:58:58 -0000 Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 53166 invoked by uid 500); 21 Apr 2004 07:58:58 -0000 Mailing-List: contact user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list user@ant.apache.org Received: (qmail 53143 invoked from network); 21 Apr 2004 07:58:57 -0000 Received: from unknown (HELO mail.tapiola.fi) (193.209.71.68) by daedalus.apache.org with SMTP; 21 Apr 2004 07:58:57 -0000 Received: from S05023 (localhost [127.0.0.1]) by mail.tapiola.fi (8.12.10/8.12.10) with ESMTP id i3L7oT7F029126 for ; Wed, 21 Apr 2004 10:50:30 +0300 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Performing unattended daily builds with WebSphere Studio and Ant Date: Wed, 21 Apr 2004 10:59:18 +0300 Message-ID: <59DDE36CD52FA34D98909970572A28A50CDE50@S05023.tapio001.tapiola.fi> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Performing unattended daily builds with WebSphere Studio and Ant Thread-Index: AcQnc84da8C90l7ES4ap91cR4iHdgAAAIn0w From: "North Alex" To: "Ant Users List" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Yes, typically we have fewer beans and our coffee consumption would be = considerably lower than yours in that case :) As the number grows = though, and also the EJB interface don't change too much, too often, = could it be reasonable to have a target that would do all refresh and = compiling except the EJBs? On the occasions where a compile error = occurs due to interface change, then those beans are generated using the = tool and selecting the culprits only. We do have smaller projects (at least bean-wise), so build times are not = such an issue ... it's nice to have an idea of what's coming up if and = when they get bigger. Actually the scripts I created here were intially meant for totally = rebuilding and deploying an EAR, it's the developers that started to add = in little bits here and there to aid other repetitive, sometimes daily, = tasks ;P <=3D Alex =3D> >-----Original Message----- >From: Andre.Fleischer.lsy@hermes-lg.de=20 >[mailto:Andre.Fleischer.lsy@hermes-lg.de]=20 >Sent: Wednesday, April 21, 2004 10:40 AM >To: Ant Users List >Subject: Antwort: RE: Antwort: Performing unattended daily=20 >builds with WebSphere Studio and Ant > > >Hi, > >we split up our build scripts, too. And I see the benefits by=20 >providing the devlepers such an aid, i would be happy if I can=20 >provide such a solution to our developers. First, main reason=20 >why I do not choose your way was the time comsuming generation=20 >of the ejb's deployment code. Whe have around 16 EJB-jars, 3=20 >Util-Jars, 1 Client-Jars, 1 EAR and 2 WARs. The 16 EJBs=20 >contains around 50 Entity-Beans, 5 Message-Beans and 30=20 >Sessions-Beans. Running a full build (refresh vom source=20 >control, compile, deployment code, creating jar) took around=20 >45 minutes. A very long time to take your coffee ;-) > >Andr=E9 --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org