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

Ralph Goers commented on LOG4J2-3483:
-------------------------------------

[~iamjamal] I suspect adding the fix version was a mistake. We typically don't 
add the fix version until we know what version it will appear in, which is 
virtually always after you see commit messages in the Jira issue.  So long as 
there are no commit messages here you should assume that no work has been done 
and the fix version is just someone's hope.

Note that no Log4j committers are directly paid to work on Log4j. We all have 
day jobs that take priority over work on Log4j. While several of us accept 
GitHub sponsorships generally that is more for thanking us for the work we do 
rather than directing what we work on. We consider all open issues to be 
important but we simply don't have time to work on everything.

> log4j-1.2-api bridge RollingFileAppender doesn't provide filePattern support
> ----------------------------------------------------------------------------
>
>                 Key: LOG4J2-3483
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3483
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Log4j 1.2 bridge
>    Affects Versions: 2.17.2
>            Reporter: Md Jamaluddin Khan
>            Assignee: Piotr Karwasz
>            Priority: Major
>             Fix For: 2.18.0
>
>
> The Builder for RollingFileAppender doesn't provide support for filePattern. 
> In case of a roll-over it uses a hardcoded pattern like 'filename+.<count>'.
> There are cases where a user would like the rolled over file to be named as 
> per a desired pattern. In absence of this option it renders the migration 
> from log4j1 to log4j2 via bridge almost impossible without breaking changes.
> Add support for filePattern in all the configurations ( XML, properties )



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to