The variable is defined in the build.xml file. The only thing the macrodef file
needs to have in advance in the name of the attribute, not the value.
--
Charles Knell
ckn...@onebox.com - email
-Original Message-
From: Mark Waschkowski
Sent: Fri, 6 Feb 2009 16:28:38 -0500
To:
Hi,
Thanks, but no.
I have my macrodefs stored in one file, and I import it in the 'real' build
file like so:
I want to pass in my 'real' build properties to the macrodefs without
defining values in the macrodef file. This works using elements, but not
with attributes - am I missing something?
I set up properties
in the "init" target and use references to them in the macrodefs.
Here's an example
I then refer to the property in the macrodef
ex.
Hi all,
First time poster, hi! Thanks to the devs for ant, been using it for years
now. I tried to do something new by creating a macrodef, but ran into some
problems with passing in a classpath, and didn't see any solutions having
gone through the mailing list archive. I've created a separate file
You can use both ...
When using namespaces use autoloading the antlib.
But you can also load the antlib in the old way
Jan
>-Ursprüngliche Nachricht-
>Von: Steve Liu [mailto:stevec...@gmail.com]
>Gesendet: Freitag, 6. Februar 2009 14:25
>An: Ant Users List
>Betreff: Re
sorry to belabor the point, but I think I'm still not quite getting it:
>No, thats right.
>If you want to use you have to have Ant 1.6 or higher (like
>current 1.7.1).
> e.g. works with older Ant versions (like 1.5).
But I can't use but only , right? I understand that the
difference is just the
