WARNING: mismatched assumptions! 8-)
> >It appears that xerces.jar is not on the classpath. Should this be in
> >the Xalan build.xml file?
> I believe it is, though I haven't traced through this. Try just saying
> "build" -- the default target -- rather than "build compile". That works
> for me, when starting with an empty classpath...
Actually, Edwin isn't using 'build' at all - he's using an installed copy
of Ant, which appears to be popular in other circles. I thought I had
convinced most Xalan developers to simply use the checked-in copy of Ant
that xml-xalan/java/bin has, but Edwin was testing the assumption that a
user-installed version of Ant should suffice.
I thought I had covered this issue, but I guess not. The issue is that Ant
needs an XML parser to parse the build.xml file itself. The Xalan build
also needs a JAXP-compilant parser to compile Xalan (and possibly we need
Xerces hard-coded for now too...), although this does not have to be the
same parser that Ant used.
I setup build.bat (and I think .sh) to try to grab a PARSER_JAR environment
variable. If it's not set, I default to the bin/xerces.jar that's checked
in. I then attempt to pass this on the command line to Ant so that
build.xml's ${parser.jar} is set appropriately. Unfortunately, I'm not
sure that I did this correctly, especially since I'm managing both the
java/build.bat and test/build.bat files, which have slightly different
assumptions. Obviously, there may be some assumptions in these files that
the user-installed ant.bat/.sh don't have, hence our problem.
Note that Xalan's build.xml files require Ant 1.4.1 or later due to use of
the <conditional> task.
Short-term workaround: use the xalan-checked-in scripts
xml-xalan/java/build.bat/.sh to build Xalan. Longer term, if anyone wants
to help dive in to clean up our build.bat/.sh/.xml files, speak up... I'm
not as much an Ant expert as I thought.
- Shane
