[Anthill] Examples of how to update CVS Working Dir script

[Holmes, Wayne]

We have run into an issue were some of our builds on our AntHill box are
failing because we end up with path names that are >255 characters
(Windows XP limit) using the default AntHill configuration. (Has to do
with building some extremely large XBEANS that have long package names.)

It looks like we can update the "CVS Working Dir" script to shorted the
value returned by baseWorkDirName, but have a couple of questions:

1) Are there some examples available of other things people have done?
2) Is the baseWorkingDir returned by "CVS Working Dir" get passed along
to the steps that follow? The reason I ask, is that I tried changing the
baseWorkDirName to point to a temp directory and while the CVS step
seemed OK the "Specificaton File Based Versioning Strategy" couldn't
find the version control file. When I went out to look on the file
system, I could see a directory created but it was empty.

Any other suggestions on how to trim the prefixing done by AntHill would
be appreciated. (And yes... we are working on reducing the size of some
of the generated packages, but the schema we are generating the XBEANS
from is part of a standards document we can't easily modify without
breaking things for our business partners.)

Thanks in advance!

Wayne L. Holmes
Lead Software Development Engineer
E-mail: wayne.holmes at qwest.com