[
https://issues.apache.org/jira/browse/LOG4J2-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414324#comment-15414324
]
Remko Popma commented on LOG4J2-1501:
-------------------------------------
Strictly speaking this isn't the API module so I see the argument that we can
break binary compatibility here, but on the other hand do we _have to_? If we
can add a builder or factory method with the additional parameter, and let the
old method delegate to the new one, there's no maintenance burden.
The possibility of breaking changes was one reason people mentioned for
hesitating to migrate to Log4j 2...
> FileAppender should be able to create files lazily
> --------------------------------------------------
>
> Key: LOG4J2-1501
> URL: https://issues.apache.org/jira/browse/LOG4J2-1501
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Reporter: Gary Gregory
> Assignee: Gary Gregory
> Fix For: 2.7
>
>
> FileAppender should be able to create files lazily.
> Add a {{lazyCreate}} attribute to {{FileAppender}}.
> If that goes well, do the same for other types file appenders (rolling and
> random access).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
