Return-Path: 
 <user-return-42981-apmail-ant-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-user-archive@www.apache.org
Received: (qmail 10354 invoked from network); 6 May 2004 21:27:08 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 6 May 2004 21:27:08 -0000
Received: (qmail 85475 invoked by uid 500); 6 May 2004 21:26:51 -0000
Delivered-To: apmail-ant-user-archive@ant.apache.org
Received: (qmail 85269 invoked by uid 500); 6 May 2004 21:26:50 -0000
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:user-unsubscribe@ant.apache.org>
List-Subscribe: <mailto:user-subscribe@ant.apache.org>
List-Help: <mailto:user-help@ant.apache.org>
List-Post: <mailto:user@ant.apache.org>
List-Id: "Ant Users List" <user.ant.apache.org>
Reply-To: "Ant Users List" <user@ant.apache.org>
Delivered-To: mailing list user@ant.apache.org
Received: (qmail 85255 invoked from network); 6 May 2004 21:26:50 -0000
Received: from unknown (HELO junior.lgc.com) (134.132.72.99)
  by daedalus.apache.org with SMTP; 6 May 2004 21:26:50 -0000
Received: from lgchvw01.lgc.com (lgchvw01.lgc.com [134.132.93.107])
	by junior.lgc.com (8.11.7/8.11.3) with SMTP id i46LPh410104
	for <user@ant.apache.org>; Thu, 6 May 2004 16:25:43 -0500 (CDT)
Received: from 134.132.93.152 by lgchvw01.lgc.com (InterScan E-Mail VirusWall
 NT); Thu, 06 May 2004 16:26:47 -0500
Received: by lgchexchbh.ad.lgc.com with Internet Mail Service (5.5.2657.72)
	id <J13SVN6Y>; Thu, 6 May 2004 16:26:47 -0500
Message-ID: <830BF4914C3C4B4EB1C438D93ABF897A67CEF6@lgchexch011.ad.lgc.com>
From: Dominique Devienne <DDevienne@lgc.com>
To: "'Ant Users List'" <user@ant.apache.org>
Subject: RE: Using nested fileset in custom ant task
Date: Thu, 6 May 2004 16:26:47 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
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

> 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