Thanks for the feedback! Tracking it here: https://issues.apache.org/jira/browse/LOG4J2-1243
Cheers Veit Am 04.01.2016 um 22:27 schrieb Remko Popma: > Looks like the properties lookup does not account fully for default values > that are themselves lookups. Can you create a Jira ticket for this? > > Thanks! > Remko > > Sent from my iPhone > >> On 2016/01/04, at 23:56, Veit Guna <[email protected]> wrote: >> >> Small correction: the system property is set via "-Dmyapp.logs=foobar", of >> course. >> Just a typo during posting... >> >> >> >> >> Gesendet: Montag, 04. Januar 2016 um 14:45 Uhr >> Von: "Veit Guna" <[email protected]> >> An: [email protected] >> Betreff: Placeholder substitution in config xml >> Hi. >> >> I'm using log4j 2.5 in a REST service. >> There I would like to use the placeholder substitution to allow >> configuration of the log location. >> >> I tried this: >> >> <Properties> >> <!-- sets the path for log4j logs: >> 1. check whether java system property myapp.logs is set. If not: >> 2. check whether the OS environment variable MYAPP_LOGS is set. If not: >> 3. use logs dir in the current directory >> --> >> <Property >> name="logsPath">${sys:mypapp.logs:-${env:MYAPP_LOGS:-logs}}</Property> >> </Properties> >> >> This seems to work quite well with the exception, if myapp.logs is set, the >> path >> ends with "}". So if I set the system property "-Depss.logs=foobar" it >> creates >> the directory "foobar}" and puts the logs into that. For the ENV substitution >> it works. It also works when NO placeholder nesting is performed. So I guess >> the problem has something todo with that. >> >> Can somebody confirm seeing the same? >> >> Thanks >> Veit >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
