summaryrefslogtreecommitdiffstats
path: root/textproc/saxon-devel
Commit message (Collapse)AuthorAgeFilesLines
* Update to 8.3hq2005-02-112-4/+4
|
* - Back out version upgrade from last commit: Saxon 8.2 requires JAXP 1.3 whichhq2004-12-302-7/+8
| | | | | | | it is not possible (AFAICT) to port for now, due to the GUI installer used by Sun. JAXP 1.3 is included in J2SE 1.5 so Saxon 8.2 will be back in the ports tree when we get a working JDK 1.5. - Rename a temporary variable to keep portlint(1) happy
* - Update to version 8.2hq2004-12-213-11/+9
| | | | - Use SUB_FILES/SUB_LIST for launcher shell script
* - Use MASTER_SITE_SOURCEFORGEhq2004-11-222-14/+14
| | | | | - Track the recent changes to java/javavmwrapper - Various cosmetic changes
* - Removed unnecessary run dependency on Xerces-J (given XML APIs and some XMLhq2004-11-092-5/+11
| | | | | | | | 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
* - Update to 8.1.1hq2004-10-275-88/+41
| | | | | | | | | | - 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
* . Alter the saxon.sh script to set the JAVAVM variable to the value chosenglewis2004-07-172-4/+5
| | | | | | | | | | by bsd.java.mk during the build. This fixes a problems where the javavmwrapper (used by the script) could have potentially picked an incorrect JDK to use. . Bump PORTREVISION. PR: 69157 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
* . Add a saxon-devel port for the development version of Saxon:glewis2004-07-075-0/+159
"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>
OpenPOWER on IntegriCloud