https://issues.apache.org/bugzilla/show_bug.cgi?id=53860
Priority: P2
Bug ID: 53860
Assignee: fop-dev@xmlgraphics.apache.org
Summary: The pdf-transcoder jar created by fop 0.94 and later
includes classes from commons and avalon
Severity: blocker
Classification: Unclassified
OS: All
Reporter: djgraff...@gmail.com
Hardware: All
Status: NEW
Version: all
Component: pdf
Product: Fop
The build for apache FOP produces a jar which includes partial subsets of
classes from commons-io, commons-logging, and avalon.
By doing this, it will potentially destabilize applications that are dependent
on these libraries.
Many web-application containers do not specifically enforce load order of jars
and as a result if the pdf-transcoder.jar from 0.94 (and whatever it is in
later releases) is loaded before the proper commons-io, commons-logging etc jar
files it will cause signature errors and other runtime errors to occur.
I discovered this while using the Eclipse BIRT Report Engine in a non-osgi
fashion within a web application. My application logic utilizes a much newer
version of commons-io.
Please remove the "import" or "merging" of these class file subsets from the
build process and add a dependency on the full jars in question.
--
You are receiving this mail because:
You are the assignee for the bug.
