Uwe, thanks for not adjusting this for now. Yaniv, see the discussion above, the property is used in Jenkins to allow to run with any other XML Parser, it verifies what Uwe adjusted and shows if there are other issues when we run with other XML Parser implementations, We can easily raise the Xerces version to something more up-to-date after 3.11 is released so we automatically verify things in the future, overall this is an easy addition to the test-suite and does a lot of additional verifying.
I agree that the version is quite outdated, but at least in my large project it was pulled in from somewhere completely unrelated, so a simple update of 3.11-beta1 to 3.11-beta2 turns out to require messing with rather unrelated dependencies and exchange of other bundles that until now still worked fine. Dominik. On Tue, Aug 19, 2014 at 11:17 AM, Nick Burch <[email protected]> wrote: > On Tue, 19 Aug 2014, Yaniv Kunda wrote: >> >> I'm not sure why the old xerces-2.6.1 jar was added to build.xml - It is >> downloaded but not included in any classpath, and does not seem to be tested >> anywhere. > > > From the svn log: > > ------------------------------------------------------------------------ > r1618610 | centic | 2014-08-18 14:59:01 +0100 (Mon, 18 Aug 2014) | 2 lines > > * Allow to start tests with old Xerces jar-file to trigger issues we saw > with missing methods in this XML parser. This is only active if the location > of the jar-file is provided via ant property > "-Dadditionaljar=lib/xercesImpl-2.6.1.jar" > * Also remove dom4j from downloaded libs to fully get rid of it in > build-environments > ------------------------------------------------------------------------ > > Does that answer your query? > > Nick > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
