ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Lindwall <JLindw...@Xifin.com>
Subject RE: Build 200 entity beans
Date Fri, 12 Apr 2002 05:08:14 GMT
Thanks!  The <ejbjar> task is just what the doctor ordered!

Our newer deployments use a single mondo ejb.jar but for old configurations I still need to
support many small ejb.jars.

John

> -----Original Message-----
> From: Erik Hatcher [mailto:jakarta-ant@ehatchersolutions.com]
> Sent: Thursday, April 11, 2002 5:25 PM
> To: Ant Users List
> Subject: Re: Build 200 entity beans
> 
> 
> Have you looked at the optional <ejbjar> task?  It should do 
> what you want,
> I believe.  Although why build an EJB JAR for each entity 
> bean rather than
> put them altogether into one?
> 
>     Erik
> 
> 
> ----- Original Message -----
> From: "John Lindwall" <JLindwall@Xifin.com>
> To: "'Ant Users List'" <ant-user@jakarta.apache.org>
> Sent: Thursday, April 11, 2002 7:48 PM
> Subject: Build 200 entity beans
> 
> 
> > Our build.xml script needs to build ejb jar files for 200 individual
> entity beans.  What is the best way to encode this in a 
> build.xml file.  I
> shudder to think of creating 200 individual targets.
> >
> > I can see creating a generic target to perform the 
> processing (mkdir, copy
> xml files, run ejbc, etc) but then I still need 200 <antcall> 
> invocations to
> process all the entity beans.
> >
> > I find myself wanting to say "foreach dir in com\beans\* call the
> entity-bean-build target".  Then I only need a  single 
> entity-bean-build
> target and I can add/remove subdirs in the source tree and 
> the build will
> automatically pick thme up.  Is this a viable idea or is 
> there some bettter
> idea.
> >
> > John
> >
> 
> 
> --
> To unsubscribe, e-mail:   
<mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message