Hmm. Not sure why you would need this - but I assume you have a reason. One way people test software versions is to look for a known file in the product's file structure and set a property if its available. I don't know how viable this approach is with ant - since i can't think of anything you could consistantly test on, other than added jar libs, and not all ant version got new libs.
There's no task available with ant to do check the version. However the version is an implicit property, so you could do some pattern matching against the property "ant.version". Have a look at the "contains" condition in the docs. [ November 24, 2004: Message edited by: Paul Sturrock ]