I ran a few tests of a recent copy of the 1.0dev
stream and found some errors.
What are your preferences for problem reports at this time ?
Should I enter issues into BugZilla as I find them ?
Should I take a look at the code and notify the committer
who last worked on anything I find ?
So far:
1) ./build.sh test <-- testing fails quickly
2) ./build.sh junit <-- are there any tests ?
3) from root directory (the one containing build.xml) I ran:
find test -name "*.fo" -print -exec ./test.sh {} \;
where test.sh contains:
#!/bin/sh
java -Xms100m -Xmx200m -cp
.:build/fop.jar:lib/avalon-framework-4.1.4.jar:lib/batik.jar:lib/commons-io-dev-20030703.jar
org.apache.fop.apps.Fop -fo ${1} -pdf /tmp/$$.pdf
I get quite a few errors.
One example problem (or non-problem):
test/xml/bugtests/image.fo
[INFO] 1.0dev
[ERROR] Error while opening stream for (file:../graphics/page.gif):
.../graphics/page.gif (No such file or directory)
java.io.FileNotFoundException: .../graphics/page.gif (No such file or
directory)
at java.io.FileInputStream.open(Native Method)
It seems that the relative file reference ../graphics/page.gif is
computed by the program relative to the 'current directory' not
relative to the file: 'test/xml/bugtests/image.fo'.
I'm sure the spec has an opinion on this. There are other errors.
(other opinions too no doubt)
test/xml/bugtests/text-transform.fo
[INFO] 1.0dev
Invalid byte 1 of 1-byte UTF-8 sequence.
Turn on debugging for more information
--
John Austin <[EMAIL PROTECTED]>
