1
0
mirror of https://git.FreeBSD.org/ports.git synced 2024-12-24 04:33:24 +00:00
Commit Graph

13 Commits

Author SHA1 Message Date
Herve Quiroz
079f1ebdc6 Fix DISTNAME now that SourceForge requires URLs ending with archive extension
PR:		96631
Submitted by:	Ion-Mihai Tetcu <itetcu@people.tecnik93.com>
2006-05-01 23:15:56 +00:00
Herve Quiroz
a55a53397f - Update to 8.7
- Use 'exec' in the launcher shell script to comply with Porter's Handbook
  guidelines
- Use OPTIONS to add support for JDom and XOM [1]

PR:		86093 [1]
Suggested by:	Rene Ladan <r.c.ladan@student.tue.nl> [1]
2006-03-22 10:46:17 +00:00
Herve Quiroz
785d2c50ef Update to 8.6.1 (maintenance release for the 8.6 branch)
Saxon 8.6.x is a complete and conformant implementation of the Candidate
Recommendations for XSLT 2.0, XQuery 1.0, and XPath 2.0 published on 3 November
2005
2005-11-24 13:22:51 +00:00
Herve Quiroz
db0b3aa954 - Update 8.5.1 (maintenance release)
- No longer install saxon8-jdom.jar ; it will be back soon but as an OPTIONal
  component

PR:		86093
Submitted by:	Rene Ladan <r.c.ladan@student.tue.nl>
2005-09-14 12:57:48 +00:00
Herve Quiroz
0088afd9aa Update to 8.5 2005-08-29 15:43:31 +00:00
Herve Quiroz
23a4fdfbaa Update to 8.3 2005-02-11 16:52:35 +00:00
Herve Quiroz
6ce928657e - Back out version upgrade from last commit: Saxon 8.2 requires JAXP 1.3 which
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
2004-12-30 23:43:44 +00:00
Herve Quiroz
b3a368ebff - Update to version 8.2
- Use SUB_FILES/SUB_LIST for launcher shell script
2004-12-21 15:43:14 +00:00
Herve Quiroz
1d99e23db6 - Use MASTER_SITE_SOURCEFORGE
- Track the recent changes to java/javavmwrapper
- Various cosmetic changes
2004-11-22 16:49:34 +00:00
Herve Quiroz
3b359db6cc - 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 16:03:39 +00:00
Herve Quiroz
5d0afe7355 - 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 16:50:43 +00:00
Greg Lewis
1f8dcb3677 . Alter the saxon.sh script to set the JAVAVM variable to the value chosen
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>
2004-07-17 08:19:44 +00:00
Greg Lewis
a03dd5e89f . 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 20:36:36 +00:00