You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/02/28 15:03:00 UTC

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

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

ASF GitHub Bot logged work on LOG4J2-2332:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 28/Feb/23 15:02
            Start Date: 28/Feb/23 15:02
    Worklog Time Spent: 10m 
      Work Description: vy closed pull request #173: [LOG4J2-2332] Unresolved variables in any file appender
URL: https://github.com/apache/logging-log4j2/pull/173




Issue Time Tracking
-------------------

            Worklog Id:     (was: 848082)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)