On Fri, 4 Nov 2005, aubie au <[EMAIL PROTECTED]> wrote:
> I tried by defining by taskdef in a different way and
> it works now. In the task definition, I dont put
> classpath and start ant -lib $MY_LIB, it works fine.
>From Ant's point of view this is more or less the same.
> Does that mean task
Hi Stefan,
Thanks for your quick response.
I tried by defining by taskdef in a different way and
it works now. In the task definition, I dont put
classpath and start ant -lib $MY_LIB, it works fine.
Does that mean taskdef implementation has a problem?
I can live with this annoyance for now, but t
On Thu, 3 Nov 2005, aubie au <[EMAIL PROTECTED]> wrote:
> In main/build.xml, I call the build targets of all
> subN using ant task(I tried subant task also).
> The problem is, when I run all subN from
> main/build.xml, ant creates a separate classloader
> (AntClassLoader2) each time i call task.
This might be a common problem you might have seen.
My project structure is like this.
main/
build.xml
config/common-targets.xml
sub1/build.xml
...
subN/build.xml
In common-targets.xml, I have my own taskdef like this
Each subN/build.xml has something like thi
