Found a good solution: Modify the xalan-test's invocation of
ResultScanner to use bootclasspath to make sure we're running our
version of the code rather than risking a mixture of ours and whatever
the JRE's TransformerFactory configuration defaults to. We were already
doing that in the tests themselves, so this is just making the scan
consistent with those other operations.
I've confirmed that this doesn't harm testing the Ant build, but does
fix the issue when testing the Maven build.
Fix has been merged into xalan-test.
With this fix in place, it *MAY* be time to start thinking about
squashing my xalan-java-mvn branch and issuing a pull request for
official review.
Of course longer term we probably want to move xalan-test into the test
trees of the maven build, so continuous integration can smoketest. But
that can be done as a subsequent pass; I haven't looked at how much
hassle adapting the test drivers (currently written as Ant tasks) will be.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
