| Commit History - (may be incomplete: see SVNWeb link above for full details) |
| Date | By | Description |
21 Mar 2013 00:24:35
  9.1.0.8,1
|
jgh  |
- adopt optionsNG
Approved by: portmgr (miwi) |
10 Dec 2012 13:43:44
9.1.0.8,1
|
bapt |
Decommissioning java 1.5 (EOLed since October 2009):
suppress any reference to JAVA_VERSION= 1.5+ (part3) |
12 Jun 2012 06:05:01
9.1.0.8,1
|
hq |
Update to 9.1.0.8
PR: 168650
Submitted by: Pedro Giffuni <giffunip@tutopia.com> |
08 Sep 2011 09:26:16
9.1.0.7,1
|
girgen |
Add missing substitution for JAVA_VERSION |
21 Jul 2011 05:03:02
9.1.0.7,1
|
linimon |
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 |
05 Jul 2011 21:01:30
9.1.0.7,1
|
hq |
- Update to 9.1.0.7
- Add support for Dom4J
PR: 158507
Submitted by: Pedro Giffuni <giffunip@tutopia.com> |
03 Jul 2011 14:40:25
8.9.0.4_1,1
|
ohauer |
-remove MD5 |
22 Aug 2009 00:37:17
8.9.0.4_1,1
|
amdmi3 |
- Switch SourceForge ports to the new File Release System: categories starting
with T,U,V |
06 Jun 2008 14:05:09
8.9.0.4_1,1
|
edwin |
Bump portrevision due to upgrade of devel/gettext.
The affected ports are the ones with gettext as a run-dependency
according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT
in Makefile (29 of them).
PR: ports/124340
Submitted by: edwin@
Approved by: portmgr (pav) |
28 Jun 2007 20:37:58
8.9.0.4,1
|
hq |
Update to 8.9.0.4 |
19 May 2007 20:32:57
8.9.0.3_1,1
|
flz |
- Welcome X.org 7.2 \o/.
- Set X11BASE to ${LOCALBASE} for recent ${OSVERSION}.
- Bump PORTREVISION for ports intalling files in ${X11BASE}. |
18 Mar 2007 11:16:58
8.9.0.3,1
|
hq |
Update to 8.9.0.3 |
04 Mar 2007 16:36:07
8.9.0.2,1
|
hq |
Update to 8.9.0.2
Reported by: portscout |
01 May 2006 23:15:56
8.7,1
|
hq |
Fix DISTNAME now that SourceForge requires URLs ending with archive extension
PR: 96631
Submitted by: Ion-Mihai Tetcu <itetcu@people.tecnik93.com> |
22 Mar 2006 10:46:17
8.7,1
|
hq |
- 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] |
24 Nov 2005 14:53:18
8.5.1,1
|
hq |
Add SHA256 info |
24 Nov 2005 13:22:51
8.5.1,1
|
hq |
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 |
14 Sep 2005 12:57:48
8.5.1,1
|
hq |
- 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> |
29 Aug 2005 15:43:31
8.5,1
|
hq |
Update to 8.5 |
11 Feb 2005 16:52:35
8.3,1
|
hq |
Update to 8.3 |
30 Dec 2004 23:43:44
8.1.1,1
|
hq |
- 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 |
21 Dec 2004 15:43:14
8.2
|
hq |
- Update to version 8.2
- Use SUB_FILES/SUB_LIST for launcher shell script |
22 Nov 2004 16:49:34
8.1.1
|
hq |
- Use MASTER_SITE_SOURCEFORGE
- Track the recent changes to java/javavmwrapper
- Various cosmetic changes |
09 Nov 2004 16:03:39
8.1.1
|
hq |
- 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 |
27 Oct 2004 16:50:43
8.1.1
|
hq |
- 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 |
17 Jul 2004 08:19:44
8.0_1
|
glewis |
. 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> |
07 Jul 2004 20:36:36
8.0
|
glewis |
. 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> |
If you buy from Amazon USA, please support us by using this link.