Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 99892 invoked from network); 24 Feb 2002 16:20:14 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 24 Feb 2002 16:20:14 -0000 Received: (qmail 25373 invoked by uid 97); 24 Feb 2002 16:20:12 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 25327 invoked by uid 97); 24 Feb 2002 16:20:11 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 25316 invoked from network); 24 Feb 2002 16:20:11 -0000 X-Authentication-Warning: localhost.localdomain: costinm owned process doing -bs Date: Sun, 24 Feb 2002 08:18:53 -0800 (PST) From: X-X-Sender: To: Ant Developers List Subject: Re: We need to stop the lies In-Reply-To: <200202240921.g1O9LqZ32235@mail012.syd.optusnet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Sun, 24 Feb 2002, Peter Donald wrote: > > > Use of a separate instance of ClassLoader for each task instance. So > > > ideally if you run velocity twice then separate ClassLoaders will be > > > created for each run. This is because some tasks use static variables > > > through dependent libraries. > > > > So, do you want in ANT that each use of each task be with a separate > > ClassLoader? That should really break everything, don't you think? > > No more than separate ClassLoaders for each library. A separate ClassLoader for each external taskdef is what ant1.4 does ( check ). A separate ClassLoader for each Task will brake inter-task communication, among other things. Maybe running each target in a different class loader, but even that is too much ( I may agree with running each call in a different class loader ). 'Static variables' are an important and usefull feature, separate ClassLoader per task would brake this as well. But if you really have a need for that, I think it's ok to do it, as long as it's not the default ( i.e. you turn it on with an option ). Ant is great because of it's flexibility. We can even make the whole ClassLoader a pluggable API, with different behaviors selected by a paticular AntLoader instance that is selected ( and run ant1.4 files with a loader that puts everything in the parent loader ) Costin -- To unsubscribe, e-mail: For additional commands, e-mail: