>When updating Ant, did you also update your ANT_HOME environment >variable to point to the new directory (probably containing the Ant >version number and hence different for the two versions)?
Yes. I'd run into that problem in the past (i.e. PATH finds version M of ant shell script, but $ANT_HOME points to version M; resulting in a screwy build) so always do the following: a) set ANT_HOME b) prepend$ANT_HOME/bin to the PATH environment variable Also one correction 1) Initially , with ant 1.7.0 we used XALAN 2.7.0 2) Wit the ant 1.8.1 version, I initially tried Xalan 2.70, but had the error. 3) I since upgraded to latest xalan (2.7.1) along with related jars (xerces, 2.9), etc. So one point of clarification for this list: -does the extension definition look correct? Do I need a prefix? Did anything change with regard to xalan extensions recently -why would xalan attribute the meethod 'formatUnicode' the DTMNodeIterator and not to the declared class. thanks will
