> If logback.groovy is inside the jar then any potential issues with logback that might arise in production can't be fixed quickly without messing with the jar...
Don't put logback.groovy in a jar then? -- View this message in context: http://logback.10977.n7.nabble.com/Groovy-configuration-includes-tp14469p14470.html Sent from the Users mailing list archive at Nabble.com. _______________________________________________ logback-user mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/logback-user
