[ http://jira.qos.ch/browse/LBCLASSIC-224?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu resolved LBCLASSIC-224. ---------------------------------- Resolution: Fixed Fixed in http://github.com/ceki/logback/commit/7480e3375fa4b
Use of default values in appender-refs --------------------------------------
Key: LBCLASSIC-224 URL: http://jira.qos.ch/browse/LBCLASSIC-224 Project: logback-classic Issue Type: Improvement Components: joran Environment: All Reporter: David Harrigan Assignee: Ceki Gulcu Attachments: 0001-Add-in-the-modified-files-for-LBCORE-154-into-the-co.patch, 0001-Revert-Fix-for-http-jira.qos.ch-browse-LBCORE-154.patch, 0001-This-is-a-cleaned-up-version-for-LBCORE-154.-It-undo.patch
This is referenced also here: http://old.nabble.com/Appender-Ref-Default-Value-to28605941.html Please can we have the ability to specify default values for appender-refs. I have a use case where we need to "bake-in" the appender during build-time. I can do this at the moment for logger level by bringing in a property file (called override.properties) that can reset the logging level (which is dependent on the deployment environment and other factors). Here is a little example: <property resource="override.properties" /> <logger name="bar.foo" level="${bar.foo.log.level:-info}" additivity="false"> <appender-ref ref="console"/> </logger> The bar.foo.log.level is defined in the override.properties file. The correct file gets inserted for each build type. I would like to do the following as well: <logger name="bar.foo" level="${bar.foo.log.level:-info}" additivity="false"> <appender-ref ref="${bar.foo.log.appender:-console}"/> </logger> So that I can tell the override where to log to (console for development or log file, or smtp, or jms, or db for other environments). This would be so neato if implemented :-) Thank you. -=david=-
-- 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