[jira] [Commented] (LOG4J2-2332) Unresolved variables in any file appender

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on LOG4J2-2332:
----------------------------------------

GitHub user Lemongrass3110 opened a pull request:

    https://github.com/apache/logging-log4j2/pull/173

    [LOG4J2-2332] Unresolved variables in any file appender

    Proposed fix for LOG4J2-2332

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Lemongrass3110/logging-log4j2 hotfix/LOG4J2-2332

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/logging-log4j2/pull/173.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #173
    
----
commit 538322198b1a94d1b2a94a799d64098db6f7d3d3
Author: Lemongrass3110 <le...@...>
Date:   2018-05-03T14:04:04Z

    Proposed fix for LOG4J2-2332

----


> Unresolved variables in any file appender
> -----------------------------------------
>
>                 Key: LOG4J2-2332
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2332
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Appenders, Lookups
>            Reporter: Philipp Schneider
>            Priority: Minor
>
> If you set up a FileAppender/RollingFileAppender or some similar file writing appenders and there are still some variables left that could not be resolved you end up creating weird directories unintentionally.
> Because of this I suggest to add validation for plugin properties that should not have any unresolved variables remaining.
> I will create a pull request on GitHub for this shortly and link it to this issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)