Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m planning to replace log4j with logback. In order to get Groovy configuration (http://logback.qos.ch/manual/groovy.html) to function, I need at least logback-0.9.22.
The problem is that Grails 1.3.x ships with slf4j-api-1.5.8 which is only enough to use logback-0.9.17 which, in turn, does not support Groovy configuration.
What does actually happen (does something break / causes unexpected situations) if I upgrade slf4j-api in Grails?
See slf4j release history at http://slf4j.org/news.html.
The 1.6.0 version lists only one incompatibility:
I guess this is the exact single reason that slf4j-api-1.5.8 and logback-0.9.22 don’t match.
So after upgrading both slf4j-api and logback everything should just work.