Andy Clark wrote: > > Besides the obvious risk that a new version of a dependent tool > may break a project build, by not checking in the build tools > it becomes impossible (or at the least, very difficult) to > recreate past builds. Our choice for Xerces builds was partly > motivated by this concern.
It is very easy to recreate past builds with released versions of Xerces, ServletAPI, and Ant. The most active developer on the Axis project prefers Crimson (small, does what we need), but I continue to prefer Xerces. One of our goals is to work with a variety of spec compliant parsers. Not standardizing on one keeps us honest. > BTW, I was trying to reproduce your Axis errors yesterday and > was having some apparant classpath problems. I'll keep trying > today to get Axis to build so that I can see if the latest code > for Xerces2 still exhibits the problems you were talking about. What platform are you developing on? Let me know and I'll send you a zip containing a small, standalone batch file or shell script and set of current jars for each dependency. - Sam Ruby --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
