Thanks for responding Ralph.
Cocoon 2.2 is using commons-logging, so in the environment shown by
your stack trace it would also be going to SLF4J and the SimpleLogger
via the jcl adapter.
I guess it would help to know what version of SLF4J is in use and
where its jars are in the various places they could be.
Maybe part of the problem is that the slf4j-log4j12 pom file on the
Maven repo has a bad checksum: -
Downloading:
http://repo1.maven.org/maven2/org/slf4j/slf4j-log4j12/1.0.1/slf4j-log4j12-1.0.1.pom
406b downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'37304fd56d9cdda797718e6710637d232986c442'; remote =
'15558150f0136e9802bb95a347e0045fb4ffe697' - RETRYING
Downloading:
http://repo1.maven.org/maven2/org/slf4j/slf4j-log4j12/1.0.1/slf4j-log4j12-1.0.1.pom
406b downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'37304fd56d9cdda797718e6710637d232986c442'; remote =
'15558150f0136e9802bb95a347e0045fb4ffe697' - IGNORING
Cocoon does not directly use Log4j. It uses an abstraction layer that
defaults to log4j. slf4j is also an abstraction layer. In the stack
trace you have shown below it is using its SimpleLogger
implementation. This can be replaced with Logback, Log4j or
java.util.logging. You might simply try replacing slf4j-simple.jar
with slf4j-log4j12.jar.
I'll give it a go but I'm not sure how to do that where Maven is
involved. I guess I change a dependency in a pom.xml file? If I don't
edit a file won't Maven simply put the old jar file in the classpath again?
I've heard that Commons Logging is now considered evil by some. Would
it make sense to try to get everything in my app to use SLF4J?
Regards,
David Legg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
