[
https://issues.apache.org/jira/browse/LOG4J2-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-1322.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.6
I've added documentation in {{src/site/xdoc/manual/migration.xml}} pertaining
to Lookups and the basic migration path. The site won't be updated until 2.6 is
released, but you can view the change
[here|https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;a=commitdiff;h=63d69aed2a6066835d0303e69a8d639763b8ec27].
If this looks good to you, please verify and close this issue.
> Missing migration information
> -----------------------------
>
> Key: LOG4J2-1322
> URL: https://issues.apache.org/jira/browse/LOG4J2-1322
> Project: Log4j 2
> Issue Type: Documentation
> Reporter: Yordan Gigov
> Assignee: Matt Sicker
> Priority: Minor
> Labels: migration
> Fix For: 2.6
>
>
> When moving our project to 2.x I discovered by way of it not behaving as
> expected, that the old way to specify variables used for the paths no longer
> works. Because Tomcat by default outputs our webapp logs wherever the current
> working directory is when launched, we set-up our file names like this
> "{{$\{catalina.base\}/logs/mail.log}}".
> However the old syntax no longer works and must now be used as
> "{{$\{sys:catalina.base\}/logs/mail.log}}".
> You should add some note in the migration page for that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
