You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Yordan Gigov (JIRA)" <ji...@apache.org> on 2016/03/19 06:22:33 UTC

[jira] [Commented] (LOG4J2-1322) Missing migration information

    [ https://issues.apache.org/jira/browse/LOG4J2-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202572#comment-15202572 ] 

Yordan Gigov commented on LOG4J2-1322:
--------------------------------------

Looks good enough. It's easy to understand and well positioned in the page.

> 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-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org