Right, I think that is the issue I've seen as well. Reverting the logging dependencies should fix the issue until we can have another look. There might be another way of solving this.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira