I have seen this before after recent message changes. I am guessing
that perhaps the tool checks the values in the jars in your classpath
instead of the build tree, but haven't verified this, because usually
when I rebuild the issue goes away. Try the following from your source
root:
svn update
rm -rf jars/*
ant all
Yes, I had the same problem too, about a month ago.
As an alternate to the 'rm -rf' command, you can do
ant clobber cleanjars cleandocs junit-clean
Which does a very thorough clean of your svn client.
thanks,
bryan
