ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@apache.org>
Subject Re: For every usage of Ant class api, different class loader
Date Mon, 09 Nov 2009 05:01:44 GMT
On 2009-11-07, Gilles Scokart <gscokart@gmail.com> wrote:

> An other aproach is to specify a loader id when declaring the tasks in the
> parent project (and make sure your inherit this id in the subclass).

IIRC Raja's problem was that static blocks didn't get re-run for
projects if the tasks where sharing the same classloader (because the
system classloader was used)

> On 2009-11-05, Raja Nagendra Kumar <Nagendra.Raja@tejasoft.com> wrote:

>> The issue we are seeing is when we load our custom tasks though
>> taskdef, new classloader is being used for every programmatic ant
>> call there fore static blocks are reinitialised for every sub ant
>> project, however when when we put it in lib or in system classpath,
>> distinct classloader is not used..hence we have issue with some
>> static code :) not being reinitialized.

loaderref would make things consistent, but different from what Raja
actually wants.

Stefan

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


Mime
View raw message