This looks like an unintentional (or at least undiscussed) break due to the packaging of log4j. I would discourage Cocoon from redirecting to logging-log4j-12 until the log4j project has had a chance to discuss the issue.
It was an unintentional breakage which was fixed even before we became aware of its effect on Cocoon. In the next gump run the problem should disappear.
Cheers,
-- Ceki G�lc�
The complete log4j manual: http://www.qos.ch/log4j/
