ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "North Alex" <>
Subject RE: Performing unattended daily builds with WebSphere Studio and Ant
Date Wed, 21 Apr 2004 07:59:18 GMT

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

<= Alex =>

>-----Original Message-----
>Sent: Wednesday, April 21, 2004 10:40 AM
>To: Ant Users List
>Subject: Antwort: RE: Antwort: Performing unattended daily 
>builds with WebSphere Studio and Ant
>we split up our build scripts, too. And I see the benefits by 
>providing the devlepers such an aid, i would be happy if I can 
>provide such a solution to our developers. First, main reason 
>why I do not choose your way was the time comsuming generation 
>of the ejb's deployment code. Whe have around 16 EJB-jars, 3 
>Util-Jars, 1 Client-Jars, 1 EAR and 2 WARs. The 16 EJBs 
>contains around 50 Entity-Beans, 5 Message-Beans and 30 
>Sessions-Beans. Running a full build (refresh vom source 
>control, compile, deployment code, creating jar) took around 
>45 minutes. A very long time to take your coffee ;-)

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message