>Thanks, that seems to work (missing a tho). I assume
>that I would do the same for ?
Yes. AC has a nice pattern:
- provide a propertiesfile with tasks for Ant < 1.6
- provide a antlib.xml with tasks for Ant >= 1.6, which includes the
properties file
(If you write your own tasks, you dont need
Thanks, that seems to work (missing a tho). I assume that I would
do the same for ?
I have a dumb question, according to this page:
http://ant-contrib.sourceforge.net/tasks/tasks/for.html
is valid for ant 1.6 or higher... so the doc is wrong?
Thanks,
Steve
On 2/5/09, Peter Reilly wrote:
>
> y
you have to use the antlib.xml form of taskdef and not the antcontrib.properties
form. The antcontrib.properties is for ant 1.5 and lower, the
antlib.xml form is for
ant 1.6 and higher.
Use the following:
@{iter}
Peter
On Thu, Feb 5, 2009 at 10:06 PM, Steve Liu wrote:
> Hi,
>
Hi,
I'm trying to get the following to work
Letter @{letter}
However, when I run it. I get:
I've searched the list, but I'm not trying anything fancy like junit... so I
can't think of any jars I could need. But here is my classpath, in case it's
My problem is pretty simple. I'd like to add the classpath to my source file
list as commented below. So far, I can't find any documentation on this. The
reason I want the classpath as a source file list is because this code will
be reused by every build script in the environment. Otherwise, I wou
On 2009-02-04, wrote:
> Hi,
> I'm using Ant 1.6 on Solaris 9. When I created a JAR file, I'm
> trying to include everything in my base directory ("basedir") as
> well as an additional properties file ...
>basedir="${build}"
> includes="${nps-config-cli
