Thanks Matthew!
That seems to have done the trick!
Would you happen to know why?
No problem. I think that, by default, Maven runs the tests in the same VM that it builds
in, which includes all of the libraries which Maven itself depends upon. Maven seems
to depend on an earlier version of Xerces than what you're using. So, by forking the
tests, your code gets its own fresh VM in which your specified Xerces version is used.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
