Bug#575411: fop: log4j not initialized correctly

Florian Haas florian.haas at linbit.com
Mon Jul 11 13:50:35 UTC 2011

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 their
> classpath to make their log4j.properties settings work.

I have no idea how intrusive that fix would be on other applications.
What the fop.sh patch does is ensure proper logging for FOP, and that's
all I really intended to do.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20110711/879bfa42/attachment.pgp>

More information about the pkg-java-maintainers mailing list