freebsd-ports/textproc/saxon-devel/files/saxon.sh.in

#!/bin/sh
#
# $FreeBSD$

IAM="`basename "$0"`"

if [ "${IAM}" = "saxon-xquery" ]
then
	LAUNCHER_CLASS="net.sf.saxon.Query"
else
	LAUNCHER_CLASS="net.sf.saxon.Transform"
fi

SAXON_CLASSPATH=""
for jarfile in %%SAXON_JARS%%
do
	SAXON_CLASSPATH="${SAXON_CLASSPATH}:${jarfile}"
done

JAVA_VERSION="%%JAVA_VERSION%%" exec "%%LOCALBASE%%/bin/java" -classpath "${SAXON_CLASSPATH}" "${LAUNCHER_CLASS}" "$@"
. Add a saxon-devel port for the development version of Saxon: "The Saxon 8.0 package is a collection of tools for processing XML documents. The main components are: - An XSLT 2.0 processor, that can be used from the command line, or invoked from a Java application by use of the standard JAXP API. Saxon can be integrated with Java applications using the JAXP API, which means it is possible for a Java application to switch between different XSLT processors without changing the application code. As well as conforming closely with the XSLT 2.0 specification, Saxon offers a number of powerful extensions. - An XPath 2.0 processor accessible via an API to Java applications. - An XQuery 1.0 processor that can be used from the command line, or invoked from a Java application by use of an API. - An XML Schema 1.0 processor. This can be used on its own to validate a schema for correctness, or to validate a source document against the definitions in a schema. It is also used to support the schema-aware functionality of the XSLT and XQuery processors. So you can use Saxon to process XML by writing XSLT stylesheets, by writing XQuery queries, by writing Java applications, or by combinations of the approaches." PR: 68637 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr> 2004-07-07 22:36:36 +02:00			`#!/bin/sh`
			`#`
- Update to version 8.2 - Use SUB_FILES/SUB_LIST for launcher shell script 2004-12-21 16:43:14 +01:00			`# $FreeBSD$`
. Add a saxon-devel port for the development version of Saxon: "The Saxon 8.0 package is a collection of tools for processing XML documents. The main components are: - An XSLT 2.0 processor, that can be used from the command line, or invoked from a Java application by use of the standard JAXP API. Saxon can be integrated with Java applications using the JAXP API, which means it is possible for a Java application to switch between different XSLT processors without changing the application code. As well as conforming closely with the XSLT 2.0 specification, Saxon offers a number of powerful extensions. - An XPath 2.0 processor accessible via an API to Java applications. - An XQuery 1.0 processor that can be used from the command line, or invoked from a Java application by use of an API. - An XML Schema 1.0 processor. This can be used on its own to validate a schema for correctness, or to validate a source document against the definitions in a schema. It is also used to support the schema-aware functionality of the XSLT and XQuery processors. So you can use Saxon to process XML by writing XSLT stylesheets, by writing XQuery queries, by writing Java applications, or by combinations of the approaches." PR: 68637 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr> 2004-07-07 22:36:36 +02:00
- Update to version 8.2 - Use SUB_FILES/SUB_LIST for launcher shell script 2004-12-21 16:43:14 +01:00			IAM="`basename "$0"`"
- Update to 8.1.1 - New launcher script 'saxon-xquery' to perform XQuery queries - PREFIX -> LOCALBASE in launcher script - (CP ; CHOWN) -> CPIO - Register run dependency on Xerces-J - Dynamic plist - More relevant homepage URL in pkg-descr - Take maintainership 2004-10-27 18:50:43 +02:00
			`if [ "${IAM}" = "saxon-xquery" ]`
			`then`
			`LAUNCHER_CLASS="net.sf.saxon.Query"`
			`else`
			`LAUNCHER_CLASS="net.sf.saxon.Transform"`
			`fi`

- Removed unnecessary run dependency on Xerces-J (given XML APIs and some XML parser are included in JDK 1.4+ Standard API) - Tweaked CLASSPATH in launcher script: Only Saxon installed JARs are indeed required for command-line operations (see above) - Added some more "" in launcher script to ensure spaces in paths and args will not break anything 2004-11-09 17:03:39 +01:00			`SAXON_CLASSPATH=""`
			`for jarfile in %%SAXON_JARS%%`
			`do`
			`SAXON_CLASSPATH="${SAXON_CLASSPATH}:${jarfile}"`
			`done`

Now that the Java 1.3 and Java 1.4 ports are deprecated and will expire soon, remove support for them from bsd.java.mk. As Jikes is not available in Java 1.5 or higher, remove it from bsd.java.mk too (suggested by hq@) and from the ports which used it (only occurences were USE_JIKES=no). Support for the Blackdown VM is also removed, as it is not available in Java 1.5 and higher. Also remove the mapping from Java 1.1-1.4 to Java 1.5+ in bsd.java.mk to detect old, broken ports; therefore bump the minimal value of JAVA_VERSION to 1.5. While here, replace static values of JAVA_VERSION in files/*.in by %%JAVA_VERSION%% . PR: ports/158969 Submitted by: rene Tested on: pointyhat-west -exp 2011-07-21 07:03:02 +02:00			`JAVA_VERSION="%%JAVA_VERSION%%" exec "%%LOCALBASE%%/bin/java" -classpath "${SAXON_CLASSPATH}" "${LAUNCHER_CLASS}" "$@"`