ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ɓukasz Kurek <>
Subject RE: Ivy triggers and scope of properties
Date Tue, 22 Jan 2008 12:14:19 GMT
> -----Original Message-----
> From: Xavier Hanin [] 
> Sent: Friday, January 18, 2008 5:09 PM
> To:
> Subject: Re: Ivy triggers and scope of properties

> <target name="test">
>   <antcall target="foo">
>     <param name="dep.module" value="module1"/>
>   </antcall>
>   <antcall target="foo">
>     <param name="dep.module" value="module2"/>
>   </antcall>
> </target>
> If this works, then it's Ivy that doesn't do what expected. 
> If it doesn't, then Ivy has nothing to do with your problem, 
> and you should look for another solution, like using a script 
> or a custom Ant task (in Java) and a true variable (which 
> would BTW make things much more readable IMHO).

I'm not sure You know that <antcall> is making a new ant project,
which means a new namespace in particular. Any changes to
properties done by targets called with <antcall> are not visible
in the project from which <antcall> is called. Mayby You should
check <runtarget>, <antcallback> and <antfetch> from ant-contib?


View raw message