>You should not need both jar files. Could you try it again eliminating >xmlParserAPIs.jar from your classpath?
That's what I tried first. No dice. I'm told that the complaint means Ant isn't finding the parser: D:\user\apache\xml-xalan\java>set parser_jar=d: \user\apache\xerces2b4\xercesImpl.jar; D:\user\apache\xml-xalan\java>build smoketest Xalan-J 2.x Build ------------- D:\user\apache\xml-xalan\java>"d:\local\apps\ibm\java13\bin\java" -mx64m -Dant.home="" -classpath "bin\ant.jar;d: \user\apache\xerces2b4\xercesImpl.jar;;d:\loca l\apps\ibm\java13\lib\tools.jar" org.apache.tools.ant.Main smoketest Buildfile: build.xml BUILD FAILED No JAXP compliant XML parser found. Please visit http://xml.apache.org for a suitable parser Total time: 0 seconds D:\user\apache\xml-xalan\java> >But the factoring has to depend on the characteristics of the >product being factored. We just don't support javax.xml.transform > stuff, so why would we distribute it? The logical approach if you're going in the direction of microoptimizing the APIs jarfile is to factor it all the way down to DOM.jar, TRAX.jar, etc. etc. (I believe that was proposed and rejected.) Failing that, I'm not entirely convinced that the minor economy of not carring a few APIs it doesn't actively need buys Xerces much real-world advantage. >ours should be as close to a proper >subset of yours as different source repositories will allow. I'm reasonably happy with that answer. Looks like we're not quite there yet, though. BTW, our solution to the "different source repositories" issue was to remove this stuff from our repository entirely. We tell folks who are building xalan to download xml-commons as well, and our batchfiles build xml-apis.jar from files found there. It isn't maximally elegant, but it sorta works... What I'd really like to see is for xml-commons itself to own the creation and maintainance of however many (or few) API and toolkit jarfiles are appropriate, and have both Xerces and Xalan simply take their most recent production release... just as Xalan takes the most recent Xerces production release when it ships a download-and-run copy. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
