[ http://jira.qos.ch/browse/LBCORE-43?page=com.atlassian.jira.plugin.system.is... ] Eduardo Ito commented on LBCORE-43: ----------------------------------- I've implemented it as sugested. The affected files are listed below and are attached in a zip file. logback-core/src/main/java/ch/qos/logback/core/joran/action/Action.java logback-core/src/main/java/ch/qos/logback/core/joran/action/PropertyAction.java logback-core/src/test/java/ch/qos/logback/core/joran/action/PropertyActionTest.java logback-core/src/test/resources/input/joran/propertyActionTest.properties Could some core developer review it, and if there is no problem, and commit it? I would like to see it in the next release.
support looking up property files from classpath resources ----------------------------------------------------------
Key: LBCORE-43 URL: http://jira.qos.ch/browse/LBCORE-43 Project: logback-core Issue Type: Bug Components: Joran Affects Versions: unspecified Environment: Operating System: Linux Platform: PC Reporter: Bruno Navert Assignee: Logback dev list Attachments: res.zip
Joran's support for property files (through PropertyAction) is useful, but it only reads filesystem files. It would be useful to be able to read classpath resources, that way the logback.xml file as well as its properties files would be located in the same place (in the class path). Furthermore, it would be useful for both resource and file lookups to perform system property resolution in the included file names. For instance: <substitutionProperty resource="config/logback/logback-${CONFIG_MODE}.properties"/> where CONFIG_MODE is a system property. In our environment this is set to something like DEV or QA or PROD, which would allow use of substitution properties that change based on the environment.
-- 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