ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chappell, Simon P" <>
Subject RE: Best Practices ANT
Date Fri, 20 Feb 2004 14:09:24 GMT

>-----Original Message-----
>From: Adam Hardy []
>Sent: Friday, February 20, 2004 7:52 AM
>To: Ant Users List
>Subject: Re: Best Practices ANT
>On 02/19/2004 04:08 PM Chappell, Simon P wrote:
>>> 4)If we are using independent build.xml for each module how to call
>>> one build.xml from other?
>> I suggest that you not do that. It's better to bring in a bre-built
>> EJB from another project than to build it upon demand. This gives you
>> a much lower coupling, allowing you to swap out the EJB with another
>> one that implements the required API. It also removes any chance that
>> the EJB might be unbuildable at that instant (build breaks do happen
>> in the real world).
>That sounds very logical advice. However this could get 
>laborious if you 
>have 1 EJB per JAR and many EJBs in your project.

True. But most modern IDEs and Source Code Management systems can assist greatly with this

>Or do you think having seperate JARs for each EJB is 
>unnecessary? Seems 
>unnecessary to me, but then I probably have less experience 
>than anyone 

My rule of thumb (that got snipped from the quote of the original email) is that each independent
unit should be built separately. I imagine that there are going to be some EJBs that can be
considered logically grouped, and you could quite safely combine those into the same project
and therefore build them simultaneously. I recall that EJBs are supposed to be in individual
JAR files, so I think that combining them into a single JAR file would be classified as a
Bad Thing(tm).

>ant 1.6.0 + java 1.4.2 on Linux 2.4.20 Debian

(Ant 1.6.1 + Java 1.4.2_03 + Mac OS X 10.3.2 :-)

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

View raw message