[xalan-test] branch master updated: Minor modification: Add buildclasspath to the ResultScanner invocation. Doesn't harm use with the Ant builds, but avoids potential TransformerFactory configuration conflicts that arise when testing the Maven build.

[jk...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jkesselm pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/xalan-test.git


The following commit(s) were added to refs/heads/master by this push:
     new 6232f569 Minor modification: Add buildclasspath to the ResultScanner invocation. Doesn't harm use with the Ant builds, but avoids potential TransformerFactory configuration conflicts that arise when testing the Maven build.
     new 2965f51f Merge pull request #4 from jkesselm/master
6232f569 is described below

commit 6232f569733b377f0bd1eb933ef87be7a4fd5e6f
Author: kubycsolutions <ke...@kubyc.solutions>
AuthorDate: Fri Oct 13 21:27:37 2023 -0400

    Minor modification: Add buildclasspath to the ResultScanner invocation. Doesn't harm use with the Ant builds, but avoids potential TransformerFactory configuration conflicts that arise when testing the Maven build.
---
 build.xml | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/build.xml b/build.xml
index 8d27d83b..fa3a4b14 100644
--- a/build.xml
+++ b/build.xml
@@ -247,7 +247,7 @@ dependencies - users must manually 'build jar' first.
         <pathelement location="${tests.extensions.build.dir}" />
         <pathelement location="${tests.bugzilla.build.dir}" />        
         <pathelement location="${tests.jira.build.dir}" />        
-        <!-- Add more pathelements if we add more Java extensions dirs -->        
+        <!-- Add more pathelements if we add more Java extensions dirs -->
     </path>
 
     <!-- Classpath used when build/running xslt20 XPath 2.0 RWAPI tests -->
@@ -1340,6 +1340,11 @@ dependencies - users must manually 'build jar' first.
         description="Alias for alltest">
     </target>
 
+    <!-- ResultScanner was failing when run against the Maven build,
+         apparently due to conflicting TransformerFactory
+         defaults. The simplest solution is to make clear that we want to use
+	 our version of Apache Xalan, by setting the Boot Class Path. 	
+    -->
     <target name="scan"
         description="Run a simple ResultScanner on a tree of test results">
         <property name="scan.outputDir" value="results-alltest" />
@@ -1347,9 +1352,13 @@ dependencies - users must manually 'build jar' first.
         <java classname="org.apache.qetest.xsl.ResultScanner" 
               classpathref="conf.class.path" 
               fork="yes" >
-              <arg line="${scan.outputDir} ${scan.logFile}"/>
+	    <bootclasspath>
+	        <path refid="boot.class.path"/>
+	    </bootclasspath>
+            <arg line="${scan.outputDir} ${scan.logFile}"/>
         </java>	 
     </target>
+
     <!-- ================================================================== -->
     <!-- Build Tests: Compile/jar targets for each 'layer' of testing code  -->
     <!-- ================================================================== -->


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xalan.apache.org
For additional commands, e-mail: commits-help@xalan.apache.org