You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by jk...@apache.org on 2025/08/17 21:23:54 UTC
(xalan-java) 03/03: Disable the cross-call to xalan-test pending decision on that.
This is an automated email from the ASF dual-hosted git repository.
jkesselm pushed a commit to branch XALANJ-2651-XALANTEST
in repository https://gitbox.apache.org/repos/asf/xalan-java.git
commit 151120b2aa83904cfb783aa07f355534204e01ff
Author: kubycsolutions <ke...@kubyc.solutions>
AuthorDate: Sun Aug 17 17:23:44 2025 -0400
Disable the cross-call to xalan-test pending decision on that.
---
integration-tests/pom.xml | 103 ++++++++++++++--------------------------------
1 file changed, 32 insertions(+), 71 deletions(-)
diff --git a/integration-tests/pom.xml b/integration-tests/pom.xml
index 0baf3fd51..7ad88d501 100644
--- a/integration-tests/pom.xml
+++ b/integration-tests/pom.xml
@@ -106,85 +106,46 @@
the test source includes proof of recent run against that
source, but deferrable.
-->
- <plugin>
- <groupId>org.codehaus.mojo</groupId>
- <artifactId>exec-maven-plugin</artifactId>
- <version>3.5.1</version>
- <executions>
- <execution>
- <id>xalan-test attempt</id>
- <phase>pre-package</phase>
- <goals>
- <goal>exec</goal>
- </goals>
- </execution>
- </executions>
- <configuration>
- <executable>ant</executable>
- <workingDirectory>../../xalan-test</workingDirectory>
- <addOutputToClasspath>true</addOutputToClasspath>
- <addResourcesToClasspath>true</addResourcesToClasspath>
- <arguments>
- <!-- Make sure we're on Ant's classpath (something that
- the front-end xalan-test/build scripts we doing).
- This arguably should not be needed (especially now
- that we should no longer need endorsed or boot path
- overrides), but without it we don't resolve the
- XSLTC transformer factory class. Yes, that means
- the xalan-test ant build is sloppy. We knew that.
- -->
- <argument>-lib</argument>
- <argument>../xalan-java/build:../build:../xalan-java/lib/endorsed:../lib/endorsed</argument>
-
- <argument>clean</argument>
- <argument>jar</argument>
- <argument>extensions.classes</argument>
- <argument>smoketest</argument>
- <argument>apitest</argument>
- <argument>conf.xsltc</argument>
- </arguments>
- </configuration>
- </plugin>
<!-- <plugin> -->
- <!-- <artifactId>maven-antrun-plugin</artifactId> -->
- <!-- <version>3.1.0</version> -->
+ <!-- <groupId>org.codehaus.mojo</groupId> -->
+ <!-- <artifactId>exec-maven-plugin</artifactId> -->
+ <!-- <version>3.5.1</version> -->
<!-- <executions> -->
<!-- <execution> -->
- <!-- <id>xalan-test attempt</id> -->
- <!-- <phase>test</phase> -->
- <!-- <configuration> -->
- <!-- <target> -->
- <!-- <!-\- <ant> task is simpler. I'd hoped it would let us shift -->
- <!-- current directory (so we didn't have to add baseDir -->
- <!-- references to supporting code that assumed execution -->
- <!-- with working directory xalan-test), but current evidence -->
- <!-- is no such luck. -->
- <!-- <subant> doesn't, but lets us control failonerror and -->
- <!-- verbose. -->
- <!-- I'm *guessing* we may want inheritall. -->
- <!-- -\-> -->
- <!-- <subant -->
- <!-- buildpath="../../xalan-test/build.xml" -->
- <!-- genericantfile="../../xalan-test/build.xml" -->
- <!-- inheritall="true" -->
- <!-- failonerror="true" -->
- <!-- verbose="true" -->
- <!-- > -->
- <!-- <target name="clean"/> -->
- <!-- <target name="jar"/> -->
- <!-- <target name="extensions.classes"/> -->
- <!-- <target name="smoketest"/> -->
- <!-- <target name="apitest"/> -->
- <!-- <target name="conf.xsltc"/> -->
- <!-- </subant> -->
- <!-- </target> -->
- <!-- </configuration> -->
+ <!-- <id>xalan-test attempt</id> -->
+ <!-- <phase>pre-package</phase> -->
<!-- <goals> -->
- <!-- <goal>run</goal> -->
+ <!-- <goal>exec</goal> -->
<!-- </goals> -->
<!-- </execution> -->
<!-- </executions> -->
+ <!-- <configuration> -->
+ <!-- <executable>ant</executable> -->
+ <!-- <workingDirectory>../../xalan-test</workingDirectory> -->
+ <!-- <addOutputToClasspath>true</addOutputToClasspath> -->
+ <!-- <addResourcesToClasspath>true</addResourcesToClasspath> -->
+ <!-- <arguments> -->
+ <!-- <!-\- Use -lib to make sure we're on Ant's classpath -->
+ <!-- (something that the front-end xalan-test/build -->
+ <!-- scripts we doing). This arguably should not be -->
+ <!-- needed (especially now that we should no longer -->
+ <!-- need endorsed or boot path overrides), but without -->
+ <!-- it the tests may not resolve the XSLTC transformer -->
+ <!-- factory class. Yes, that means the xalan-test ant -->
+ <!-- build is sloppy. We knew that. -->
+ <!-- -\-> -->
+ <!-- <argument>-lib</argument> -->
+ <!-- <argument>../xalan-java/build:../build:../xalan-java/lib/endorsed:../lib/endorsed</argument> -->
+
+ <!-- <argument>clean</argument> -->
+ <!-- <argument>jar</argument> -->
+ <!-- <argument>extensions.classes</argument> -->
+ <!-- <argument>smoketest</argument> -->
+ <!-- <argument>apitest</argument> -->
+ <!-- <argument>conf.xsltc</argument> -->
+ <!-- </arguments> -->
+ <!-- </configuration> -->
<!-- </plugin> -->
</plugins>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xalan.apache.org
For additional commands, e-mail: commits-help@xalan.apache.org