Jeremias Maerki wrote:
- Our test code has a (useful) dependency on Xalan's XPath API. Java 1.4 provides an old JAXP version without XPath support (javax.xml.xpath, available with Java 1.5). So we've got a problem here for the time being.
Although it is valuable that users can run the test cases, I don't see it as a "production" activity, and we could just require them to use Java 1.5 in this case.
2. Move the 4 JARs to a lib/endorsed directory and adjust our scripts to insert them into the bootclasspath
...
- User might wonder why the JARs are suddenly in a different place.
Even worse, this might affect unrelated code for no obvious (to the user) reason.
I guess it's clear that only solution 2 makes sense if we want to change something.
I'm not really fond of this idea. I think the simplest solution is to remove the jars, and require developers and curious users who want to run tests to use a 1.5 or newer environment for this. An ant trap testing for the critical JAXP classes can prevent running the tests in older environments. J.Pietschmann
