Often you can get away with just compiling the changed source:
- find the changed Java source by browsing svn (using the link
labelled "Directory revision:")
- copy it into a folder of your choice
- put that folder into your CLASSPATH before the Saxon entries
- sitting in that folder, invoke an appropriate Java compiler:
javac -d . *.java
Be aware that a fix may or may not be dependent on other fixes.
Maybe you can find cases where this approach is insufficient, but
most of the time you should be OK with it.
Software AG - Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany, - Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/ Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), David Broadbent, Mark Edwards, Dr. Peter Kurpick, David Mitchell, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/ Chairman of the Supervisory Board: Frank F. Beelitz - http://www.softwareag.com
[mailto:saxon-help-bounces@...] On Behalf Of Michael
Sent: Tuesday, March 04, 2008 2:11 PM
To: johannes.neubauer@...; 'Mailing list for the SAXON
XSLT and XQuery processor'
Subject: Re: [saxon] Compilation error; locator returns empty
SystemID;Moved from: xsl-list@...
I'm afraid building Saxon from source is not for the faint-hearted.
Firstly, you need to use the latest9.0 branch in SVN.
There are two ways you can build Saxon. You can either start with one of
the ant scripts that I have published from time to time, for example
there is one in the latest8.9 branch in SVN, and modify it as required.
Or you can load all the code into your IDE, and then either remove
packages that you don't need (such as dotnet, jdom, xom, etc), or add
the libraries that they depend on. The second approach is probably
easier, because the ant build includes a lot of complex stuff for
building the .NET and SA versions of the product, and the documentation,
sample applications etc.
It would be nice to have a simplified ant script that just builds
Saxon-B on Java, which is what most people need, but I haven't got
around to it, and it would require a fair bit of testing to get it
> Okay, I checked out the trunk from
> 'https://saxon.svn.sourceforge.net/svnroot/saxon/trunk' and found the
> source in folder 'bj'. But there's no ant build.xml or maven pom.xml.
> So ~ I tried to compile it by hand (but my compile-by-hand abilities
> are a bit rusty):
> workspace/saxon/bj$ find net/sf/saxon/ -name "*.java" | xargs javac -d
> ../bin -sourcepath .
> But I got 100 compile errors. I recognized that there are packages
> called xom, dotnet, ...
> The classes in these packages seem to have dependencies, not covered
> by the JRE. So what do I have to put to the classpath or vchange in my
> compile command. Or are there any snapshot-releases, that I might use?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> -----END PGP SIGNATURE-----