Hi Gary, > > On Wed, Feb 1, 2023, 12:51 Gary Gregory <garydgreg...@gmail.com> wrote: > >> > >> I'm missing something: > >> > >> "Certain XalanJ "api" tests were causing these issues, and I've now > >> omitted those "api" tests from XalanJ tests configuration." > >> > >> So when are these test run? > > What about this question above?
Currently, the XalanJ tests that run with command "build apitest", are configured within xalan-test repo's file test.properties (specified at bottom of this file, with comments # Various tests, that run for ant build.xml's "apitest" target. This configuration has been introduced, starting with XalanJ 2.7.3 release). We've recently discovered that, the test SystemIDResolverAPITest from this set, is not producing same results on windows and Linux. Joseph Kessselman thinks that, XalanJ codebase within the file SystemIDResolver.java that's been tested by the test class SystemIDResolverAPITest, might have a bug. Following is an excerpt about usages within XalanJ implementation, of the Java class SystemIDResolver, [image: systemidresolver.png] This shows that, Java class SystemIDResolver is used extensively within XalanJ codebase. I think, if needed, we should fix any implementation within XalanJ class SystemIDResolver with caution as lot of XalanJ functionality is depending on this class. -- Regards, Mukul Gandhi
