Joe -- It would be hard to recheck my assertion since I never checked it in the first place. :)
It seems that, at the time, there were compile-time dependencies when Costin was doing this work. When I sent my original message, I was only going by Costin's commit message: 3 small fixes to the build process ( to make it work with jdk1.4 and crimson) - exclude IncrementalSAXSource_Xerces if xerces is not detected ... Upon review, revision 1.3 of IncrementalSAXSource_Xerces did have compile-time dependencies on the xerces SAXParser class. That is the revision that was picked up by Sun. Even if current versions of the class don't have compile-time dependencies, the revision used at the time did. Shane -- Since Joe has removed compile-time dependencies from IncrementalSAXSource_Xerces, perhaps we (ie you) should delete this line in build.xml. While you're at it, you can also eliminate the exclude for CoroutineSAXFilterTest and CoroutineSAXParser_Xerces since those don't even exist anymore. This should then allow you to eliminate the xerces.present property altogether. Gary -----Original Message----- From: Joseph Kesselman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 17, 2002 10:14 AM To: [EMAIL PROTECTED] Subject: RE: Xerces, Xalan, and 1.4.x JDK's > Although including the class would have resulted in no run-time > dependencies, there would still have been a compile-time dependency > which Costin did not want, as I recall. Please recheck that assertion. IncrementalSAXSource_Xerces is heavily laden with reflection code to avoid having a dependency upon any particular verion of Xerces.. and I _think_ that's so thoroughly encapsulated that there are no compile-time dependencies remaining. ______________________________________ Joe Kesselman / IBM Research
