ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barnhill" <>
Subject Re: Available task status and question
Date Sun, 28 May 2000 00:32:47 GMT
The AvailableEx task will be done by end of weekend. Named AvailableEx
for now, because it is not really an extension of Available but a task
that does what Available does in a different way.  This can handle
anything Available can, but also handles checking for multiple files,
resources, and classes.  Added one item to core file ProjectHelper, an
invocation of setGeneric(String attr, String value) if that method
exists in the task and no setter for the current attribute is found.
AvailableEx treats any attribute coming in this way as a list of items
to check availability of.  The attribute name is used to get the class
to actually do the check and if the class is in the classpath it is
used (if not a warning is logged and that attribute ignored).  Any
check can have one item or a comma delimited list of items.  Also it
maintains a count of checked and found items and will set the property
depending on which case occurs : All items found, No items found, more
found than not, more not found than were.  The value to set the
property to is settable for each case and defaults to
true,false,false,false respectively.  I'll post several examples when
I post the files.

Ithought Ant was designed for jdk1.2.x and greater and then I saw
where it checks the version and only says ant is incompatible if
version is 1.0.  I am currently using the jdk1.2 Collection API and
would like to keep using it, but if I have to maintain total
compatibility with 1.1.x  then I should probably convert my code to
use the 1.1 classes only and not take advantage of the new API.

There is a question in there...Can I use 1.2 or higher classes in ant,
or only 1.1 compatible?

Thanks in advance,
Bill Barnhill

View raw message