Bug#586288: fop: log4j not initialized correctly

[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 work.

As an added bonus it avoids loading lots of JAR for
nothing in the JVM (servlet-api) and might event prevent
problems.
On my setup, running fop loads both
servlet-api2.4 and servlet-api2.5. Can't this cause
problems for example in an application using
the servlet 2.5 API (in case the 2.4 is used by the
classloader) or the 3.0 servlet API ?

--
Gabriel