Hi Fred,
I just did a clean checkout of the docs, did a build, and had the same failure unless I moved xerces related jars with the buffer fix to it into the ant directory (or CLASSPATH). Although I don't see this as the problem you are currently having.
Jean said a build under fedora core 3 worked.
My current Fedora core 3 uname -a
Linux scott.mprojects.wiu.edu 2.6.10-1.770_FC3 #1 Thu Feb 24 14:00:06 EST 2005 i686 i686 i386 GNU/Linux
I'll have to try on a fedora core 3 machine at home and see how that goes.
The only thing that SHOULD cause this problem (besides some older jars) would be character encoding.
use locale to check character encoding. A locale set as nothing (in the past) would cause jvm failure on startup. So locale does matter :-) Possibly a problem with character encoding exists (my last, somewhat fair guess that I can think of).
locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=
Fred Baube wrote:
As suggested by J.Levitt (his message is included below), I have re-verified my installation.
- I unzipped the DITA-OT 1.0 distro under Derby's trunk/
- ant is 1.6.2:
>> ant -version Apache Ant version 1.6.2 compiled on July 16 2004
- Paths are correct:
>> echo $CLASSPATH
/opt/trunk/lib/avalon-framework-cvs-20020806.jar:/opt/trunk/lib/batik.jar:/opt/trunk/lib/fop.jar:/opt/DITA-OT1.0/lib/dost1.0.jar:/opt/j2sdk1.4.2_07/jre/lib/rt.jar
>> echo $PATH /usr/local/apache-ant-1.6.2/bin/:/opt/j2sdk1.4.2_07/bin/:~/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11
- I have just today updated my Derby installation:
>> svn update At revision 159582.
With all this, I am still getting the same error as before.
I also tried the DITA OT 1.0.1beta, and get the same errors.
Perhaps it is a problem somehow unique to my installation (on Debian testing).
thank you all for the assistance,
fred baube
Quoting Jeff Levitt:
--- Fred Baube <[EMAIL PROTECTED]> wrote:
To clarify ...
/opt/trunk >> echo $CLASSPATH/opt/trunk/DITA-OT1.0/xsl/preprocess/topicpull.xsl
/opt/DITA-OT1.0/lib/dost1.0.jar: [..]
[xslt] Loading stylesheet
The following error occurred while executing this
line:/opt/trunk/DITA-OT1.0/pretargets.xml:120: javax.xml.transform.TransformerException: java.lang.NullPointerException
I have a symlink from
/opt/trunk/DITA-OT1.0 to /opt/DITA-OT1.0
so, the CLASSPATH does in fact include the "dost" jar of the new DITA-OT release.
I'm not sure I understand everything you are doing with CLASSPATH etc, Fred. I didn't do anything with the Toolkit myself in regards to CLASSPATH. Let me tell you how I set my environment up, and maybe you can mirror it and get better results:
Starting with a clean directory, I checked out the dita files (which include FOP and the ant build file). I then download the DITA Toolkit to the TRUNK directory. Use ONLY the Dita 1.0 toolkit, do not use the beta toolkit. The final path is:
trunk\DITA-OT1.0\
There is nothing else to do with the toolkit.
For CLASSPATH, if ant is already installed and set up in the CLASSPATH, all you need to add are the 3 FOP jar files in the trunk/lib/ directory.
That's IT. There should be nothing else you need to do.
Can you try that, or let me know if there's something
I'm missing that you have to do in your environment? My problem is that I am less experience with Linux
than I am with Windows...
