[ http://jira.qos.ch/browse/LBCORE-254?page=com.atlassian.jira.plugin.system.i... ] Ceki Gulcu commented on LBCORE-254: ----------------------------------- Hello Erle, As demonstrated by sysProps() in JoranConfiguratorTest [1], system properties are interpreted correctly in the "file" attribute of the <property> element. Please provide a test case demonstrating the problem. In the absence of such a test, I intend to resolve this issue as "cannot reproduce". [1] https://github.com/ceki/logback/blob/master/logback-classic/src/test/java/ch...
Logback cannot read system properties configured in Maven Jetty Plugin ----------------------------------------------------------------------
Key: LBCORE-254 URL: http://jira.qos.ch/browse/LBCORE-254 Project: logback-core Issue Type: Bug Reporter: Erle Czar Mantos Assignee: Logback dev list
I have a system property configured in the maven jetty plugin, as follows: <plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>maven-jetty-plugin</artifactId> <version>6.1.10</version> <configuration> <systemProperties> <systemProperty> <name>project.home</name> <value>D:</value> </systemProperty> </systemProperties> .... </configuration> </plugin> If I use this system property in logback -- <property file="${project.home}/foo/bar/baz/app.properties"/> This system property is UNDEFINED when I run the webapp via mvn jetty:run. The rest of the system (spring configuration files, etc) can happily use the project.home system property except for logback. The only way to run jetty now, with the correct substitution is through: mvn jetty:run "-Dproject.home=D:"
-- 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