Bug#575411: fop: log4j not initialized correctly

2011-09-15 Thread Gabriel Corona
Patch dump_exception.patch is probably redundant with a working logging configuration (3 lines below the exception is logged). Moreover, it should not print traces to stdout (the real output of fop might be sent there). -- Gabriel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.de

Bug#575411: fop: log4j not initialized correctly

2011-09-15 Thread Gabriel Corona
In fact the bug is not fixed by FOP 1.0. It is fixed by Debian patch 04_fixqdoxbuildfailure.patch : [...] --- /dev/null1970-01-01 00:00:00.0 + +++ fop-1.0/fop.mf2011-08-26 15:15:10.0 +0200 @@ -0,0 +1,1 @@ +Class-Path: xercesImpl.jar xalan2.jar bsf.jar avalon-framework.j

Bug#575411: fop: log4j not initialized correctly

2011-09-11 Thread Mathieu Malaterre
tag 575411 moreinfo thanks For some reason I cannot reproduce this issue with latest fop from testing. Could someone double-check ? Thanks much -- Mathieu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.

Bug#575411: fop: log4j not initialized correctly

2011-07-11 Thread Florian Haas
On 2011-07-11 15:42, Gabriel Corona wrote: > Hello, > > Shouldn't this be fixed in commons-logging ? > > Removing the classpath entry from MANIFEST-MF > (06_classpath_manifest.patch in commons-logging) > should fix the problem in applications. > Individual applications might want to add log4j in

Bug#575411: fop: log4j not initialized correctly

2011-07-11 Thread Gabriel Corona
Hello, Shouldn't this be fixed in commons-logging ? Removing the classpath entry from MANIFEST-MF (06_classpath_manifest.patch in commons-logging) should fix the problem in applications. Individual applications might want to add log4j in their classpath to make their log4j.properties settings wor

Bug#575411: fop: log4j not initialized correctly

2010-06-18 Thread Vincent Fourmond
clone 575411 -1 reassign -1 libbatik-java thanks Hi, On Fri, Jun 18, 2010 at 1:36 AM, Gabriel Corona wrote: > A quick fix is to add either : > -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog > or > -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk1

Bug#575411: fop: log4j not initialized correctly

2010-06-17 Thread Gabriel Corona
Hello, A quick fix is to add either : -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog or -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger in the last command of /usr/bin/fop : run_java -Dorg.apache.commons.logging.Log=org.apache.commons.loggin

Bug#575411: fop: log4j not initialized correctly

2010-03-25 Thread brian m. carlson
Package: fop Version: 1:0.95.dfsg-10 Severity: normal The following warnings occur every time I run fop: lakeview ok % fop -v 2>&1 | head -n 2 log4j:WARN No appenders could be found for logger (org.apache.fop.util.ContentHandlerFactoryRegistry). log4j:WARN Please initialize the log4j syste