[ http://jira.qos.ch/browse/LBCORE-172?page=com.atlassian.jira.plugin.system.i... ] Ceki Gulcu commented on LBCORE-172: ----------------------------------- Hi Anthony, The compiled code would still need groovy-all.jar on the classpath wouldn't it?

Compile logback.groovy rather than interpret at runtime -------------------------------------------------------

Key: LBCORE-172 URL: http://jira.qos.ch/browse/LBCORE-172 Project: logback-core Issue Type: Improvement Components: Other Affects Versions: 0.9.25 Environment: Windows, Java 6 Reporter: Anthony Whitford Assignee: Logback dev list Priority: Minor

Configuring LogBack using an internal DSL with Groovy is a clever idea. Rather than including logback.groovy in the classpath and requiring a 5.5 MB groovy-all dependency to load and interpret it, why not offer a way that logback.groovy could be compiled at compile time. Then, instead of interpreting logback.groovy using a GroovyShell, why not simply run a method from an already compiled class. This strategy has the advantage of discovering many configuration problems (like typos) at compile-time rather than run-time.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira