In fact the bug is not fixed by FOP 1.0. It is fixed by Debian patch 04_fixqdoxbuildfailure.patch :
[...] --- /dev/null 1970-01-01 00:00:00.000000000 +0000 +++ fop-1.0/fop.mf 2011-08-26 15:15:10.000000000 +0200 @@ -0,0 +1,1 @@ +Class-Path: xercesImpl.jar xalan2.jar bsf.jar avalon-framework.jar batik.jar commons-io.jar commons-logging.jar xmlgraphics-commons.jar xml-commons-external.jar A "log.properties" file is now found in bsf.jar which is now in the classpath and found by log4j. You can find this by running fop 1:1.0.dfsg2-2 with -Dlog.debug : log4j: Using URL [jar:file:/usr/share/java/bsf.jar!/log4j.properties] for automatic log4j configuration. The FOP CLI behaviour should probably not depend on bsf logging configuration, it doesn't seem very robust. Moreover, the configuration from bsf.jar does not log warnings. Adding -Dorg.apache.commons.logging.Log=org.apache.fop.util.CommandLineLogger would use the default logger for fop CLI. -- Gabriel Corona -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
