Implement Grails like Capability to Change Logging Backends

Andres Almiray added a comment - 14/Jan/12 9:19 AM Instructions as explained on that blog post do work for Griffon too. 1. Exclude log4j dependencies from global space, but do not exclude log4j-1.2.16 as it will cause a CNFE at runtime (some classes are required by the logging DSL). 2. configure Logback in the dependency DSL, like this griffon.project.dependency.resolution = { inherits( "global" ) { excludes 'slf4j-log4j12', 'log4j-over-slf4j' } log "warn" repositories { griffonHome() mavenCentral() } dependencies { String logbackVersion = '1.0.0' build "ch.qos.logback:logback-core:$logbackVersion" , "ch.qos.logback:logback-classic:$logbackVersion" runtime "ch.qos.logback:logback-core:$logbackVersion" , "ch.qos.logback:logback-classic:$logbackVersion" } } 3. Create a suitable Logback configuration in griffon-app/conf/resources/logback.xml <configuration debug= " true " scan= " true " scanPeriod= "30 seconds" > <appender name= "STDOUT" class= "ch.qos.logback.core.ConsoleAppender" > <layout> <pattern>%d{HH:mm:ss.SSS} %-5level %logger{36} - %msg%n</pattern> </layout> </appender> <logger name= "griffon" level= "INFO" /> <logger name= "org.codehaus.griffon" level= "DEBUG" /> <root level= "warn" > <appender-ref ref= "STDOUT" /> </root> </configuration> 4. Profit!

Richard Freedman added a comment - 18/Oct/12 9:40 AM I found that for Griffon, putting a logback.groovy DSL config file in griffon-app/resources works. I haven't tried it for Grails yet, YMMV.