Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Users List" <user@ant.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
From: Stefan Bodewig <bodewig@apache.org>
To: user@ant.apache.org
Subject: Re: Recycle an Ant task
References: 
 <CAPnWRSOUWMwPd55SvSKZpNF8K1zatOEfp50jX3BdFc2RmHFARg@mail.gmail.com>
Date: Fri, 28 Sep 2012 06:08:15 +0200
In-Reply-To: 
 <CAPnWRSOUWMwPd55SvSKZpNF8K1zatOEfp50jX3BdFc2RmHFARg@mail.gmail.com>
	(Jose Rojas's message of "Wed, 26 Sep 2012 14:45:24 -0700")
Message-ID: <87y5jueqmo.fsf@v35516.1blu.de>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

On 2012-09-26, Jose Rojas wrote:

> I would like to create a custom ant task that caches some results from an
> operation and saves it for use in future executions.  My simple method of
> doing this is using a 'static' member.  This would work great for me as the
> operations would be appropriate to cache at an application wide level.

A better approach might be to store the data as a reference in the
Project instance (or several of them).

> However what I'm noticing is that for each new execution of Ant (I'm using
> the Ant taskdef to execute ant), the static data is lost, quite possibly
> caused by Ant creating a new class loader upon every execution, thus not
> reusing my ant task class instance from the previous execution.

This would happen if you use multiple taskdefs - i.e. repeat it several
times.  You can pass a name of a class loader to taskdef (the loaderRef
attribute) and Ant will create a class loader on the first execution,
cache it and reuse it for all subsequent task/typedefs that use the same
name.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org