Hi Sam, I did it a couple of days ago, it's in 1.4beta1 and thus in cvs. It works w/ both Trax and xalan1. It checks first for Xalan2, if it fails it checks for Xalan1..if it fails you're done. Unless I forgot something...of course. When it runs it prints the xalan version with the transformation time you can't miss it.
I'm having a hard time right now to convert all xsltliaison to something that will work in all cases due to systemid problems in xalan2, that will close the handle to the file immediately (otherwise xalan relies on garbage collector to close the stream), and that will do a correct UTF8 output.... Stephane ----- Original Message ----- From: "Sam Ruby" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, August 11, 2001 10:10 PM Subject: Anybody object to my converting junit.AggregateTransformer over to TRaX? > It should be a straightforward change. I don't honestly care if it makes > 1.4 or is post 1.4 (I run from CVS anyway... ;-)). > > Xalan1 is essentially retired at this point...the last release of that was > a year ago, and the code has even been removed from cvs. > > - Sam Ruby
