Formatting test/resources/fop/image/errors.fo using command-line Fop encounters an error, then throws an IOException and produces a stack trace followed by more of the error. Shouldn't we skip the Exception.printStackTrace() where the root cause is well-understood and handled by the program ? Command to cause this problem: ============================== 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 test/resources/fop/image/errors.fo -pdf /tmp/12610.pdf [INFO] 1.0dev [WARNING] Error while constructing image from XML java.io.IOException: Stream closed ... stack trace deleted ... [ERROR] No ImageReader for this type of image (file:corrupt.svg) ... more stack trace deleted ... the same error is repeated (I think),
Created attachment 9499 [details] Log of messages including the error and stack trace
Created attachment 28579 [details] fop 1.1dev log the current output when running FOP1.1dev (trunk) on input file and images
Created attachment 28580 [details] input test files
moving to resolved+wontfix due to lack of action or agreement to take action on this; i've attached a full input test set plus the current console output from fop1.1dev trunk
batch transition resolved+wontfix to closed+wontfix
batch transition resolved+wontfix to closed+wontfix; if you believe this remains a bug and can demonstrate it with appropriate input FO file and output PDF file (as applicable), then you may reopen