I seem to be getting a successful maven build at least of interpretive
Xalan, though without the serializer jarfile.
Ran the maven build in a separate directory to get
apache-xalan-j-2.7.1-maint-main-2.7.1-SNAPSHOT.jar. Copied that over the
xalan.jar file in my normal xalan-java build directory, then popped over
to xalan-test and ran the smoketests. They report successful.
I'm more nervous about xsltc mode, since that's where the sensitivities
to java_cup appear. I *think* I've got a reasonable version of that and
jlex successfully being pulled off the maven repository, but they're not
identical to what we've been using. And they're an unofficial
repackaging of the java_cup code into maven form; caveat hackitor.
The fact that the new xalan jarfile is a bit smaller than the old one
definitely makes me nervous. And I'm not sure whether my test ran with
the existing serializer.jar, or if the build bundled the serializer into
xalan.jar *AND* shrunk.
Pasting the prototype pom.xml here in case anyone's willing and able to
sanity-check:
<project xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd";>
<!-- KNOWN ISSUES: brazil dependencies; splitting output into
serializer.jar and xalan.jar, full testing still needed.
-->
<modelVersion>4.0.0</modelVersion>
<groupId>apache-xalan-j-2.7.1-maint-main</groupId>
<artifactId>apache-xalan-j-2.7.1-maint-main</artifactId>
<version>2.7.1-SNAPSHOT</version>
<name>Apache Xalan-Java 2.7.1</name>
<description>Apache's XSLT processor</description>
<build>
<sourceDirectory>src</sourceDirectory>
<resources>
<resource>
<directory>src</directory>
<excludes>
<exclude>**/*.java</exclude>
</excludes>
</resource>
</resources>
<plugins>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.8.1</version>
<configuration>
<source>1.8</source>
<target>1.8</target>
</configuration>
</plugin>
<!-- https://github.com/vbmacher/cup-maven-plugin -->
<plugin>
<groupId>com.github.vbmacher</groupId>
<artifactId>cup-maven-plugin</artifactId>
<version>11b-20160615-2</version>
<executions>
<execution>
<goals>
<goal>generate</goal>
</goals>
</execution>
</executions>
<configuration>
<className>XPathParser</className>
<symbolsName>sym</symbolsName>
<cupDefinition>./src/org/apache/xalan/xsltc/compiler/xpath.cup</cupDefinition>
<!-- NOTE: There is an XPathParser.java in both xalan/xsltc/compiler/
and
xpath/compiler/. In our ant build, THEY ARE NOT IDENTICAL.
GONK??? -->
<outputDirectory>${project.build.directory}target/src/org/apache/xalan/xsltc/compiler</outputDirectory>
</configuration>
</plugin>
</plugins>
</build>
<dependencies>
<!-- https://mvnrepository.com/artifact/org.apache.bcel/bcel -->
<dependency>
<groupId>org.apache.bcel</groupId>
<artifactId>bcel</artifactId>
<version>6.7.0</version>
</dependency>
<!--
https://mvnrepository.com/artifact/commons-logging/commons-logging -->
<dependency>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
<version>1.2</version>
</dependency>
<!-- https://mvnrepository.com/artifact/org.mozilla/rhino -->
<dependency>
<groupId>org.mozilla</groupId>
<artifactId>rhino</artifactId>
<version>1.7.14</version>
</dependency>
<!-- https://mvnrepository.com/artifact/org.apache.bsf/bsf-api -->
<dependency>
<groupId>org.apache.bsf</groupId>
<artifactId>bsf-api</artifactId>
<version>3.1</version>
</dependency>
<!-- https://mvnrepository.com/artifact/javax/javaee-api -->
<dependency>
<groupId>javax</groupId>
<artifactId>javaee-api</artifactId>
<version>6.0</version>
<scope>provided</scope>
</dependency>
<!-- https://mvnrepository.com/artifact/javax.servlet/servlet-api -->
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
<version>2.5</version> <!-- jakata servlet is at 6.0 -->
<scope>provided</scope>
</dependency>
<!-- https://mvnrepository.com/artifact/xerces/xercesImpl -->
<dependency>
<groupId>xerces</groupId>
<artifactId>xercesImpl</artifactId>
<version>2.12.2</version>
</dependency>
<!-- https://mvnrepository.com/artifact/xml-apis/xml-apis -->
<dependency>
<groupId>xml-apis</groupId>
<artifactId>xml-apis</artifactId>
<version>1.4.01</version>
<!-- We were actually using 1.4.02, not on Maven. -->
</dependency>
<!-- https://github.com/vbmacher/cup-maven-plugin -->
<!-- We probably shouldn't be shipping java-cup itself, just
the runtime, but this makes the build work -->
<dependency>
<groupId>com.github.vbmacher</groupId>
<artifactId>java-cup</artifactId>
<version>11b-20160615-2</version>
</dependency>
<dependency>
<groupId>com.github.vbmacher</groupId>
<artifactId>java-cup-runtime</artifactId>
<version>11b-20160615-2</version>
</dependency>
<!-- Where does Apache regex.zip come from? -->
<!-- jar-download.com claims: -->
<dependency>
<groupId>regexp</groupId>
<artifactId>regexp</artifactId>
<version>1.3</version>
</dependency>
<!-- Where does Brazil come from? Needed only for xsltc sample. -->
</dependencies>
</project>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
