ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan.Mate...@rzf.fin-nrw.de
Subject RE: Using nested fileset in custom ant task
Date Fri, 07 May 2004 05:14:19 GMT
Ok - little commercial:

Tutorial: Tasks using Properties, Filesets & Paths
http://cvs.apache.org/viewcvs.cgi/*checkout*/ant/docs/manual/tutorial-tasks-
filesets-properties.html?content-type=text%2Fplain&rev=1.4

Jan

> -----Original Message-----
> From: Dominique Devienne [mailto:DDevienne@lgc.com]
> Sent: Thursday, May 06, 2004 11:27 PM
> To: 'Ant Users List'
> Subject: RE: Using nested fileset in custom ant task
> 
> 
> > From: Richard_Landon@capgroup.com 
> [mailto:Richard_Landon@capgroup.com]
> > 
> > Thank-you kind sir. I have a target to "install" the custom 
> tasks into the
> > local ant library path. Since this is picked up first, my 
> changes to code
> > that got put into the local jar (during a "dist" target) 
> were not, as you
> > suggested, being picked-up.  Do you think the 
> "install-uninstall" tasks
> > are dangerous?
> 
> I'm not following too well here ;-)
> 
> There are two ways to use custom tasks as I see it:
> 
> 1) These tasks are compiled and used on the fly.
>    In the same build that will use the task, you simply make sure
>    the task is compile and taskdef'd before it's first use. It thus
>    never needs to be on the system classpath for Ant.
> 
> 2) The tasks are compiled and packaged in a separate build
>    from the build that will use the tasks.
>    You build your tasks using a regular Ant build that does not depend
>    on these new custom tasks, and 'install' them somewhere (JAR'd up)
>    so that all other builds can use them.
> 
> Using either of these two avoids having both an old and new version of
> the custom task on the classpath at the same time.
> 
> Lets hope this somehow answers the question I didn't 
> understand ;-))) --DD
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
> 

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