You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4net-dev@logging.apache.org by "Stefan Bodewig (JIRA)" <ji...@apache.org> on 2017/03/08 12:02:38 UTC

[jira] [Commented] (LOG4NET-557) Create a Replacement/Alternative to RollingFileAppender that works

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

Stefan Bodewig commented on LOG4NET-557:
----------------------------------------

https://issues.apache.org/jira/browse/LOG4NET-427?jql=text%20~%20%22RollingFileAppender%22%20and%20project%20%3D%20Log4net%20and%20status%20%3D%20Open lists 45 issues as of this writing.

> Create a Replacement/Alternative to RollingFileAppender that works
> ------------------------------------------------------------------
>
>                 Key: LOG4NET-557
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-557
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders
>            Reporter: Stefan Bodewig
>              Labels: RollingFileAppender
>
> The number of bugs raised against {{RollingFileAppender}} is pretty huge and it is full of bad assumptions. I (Stefan) am convinced that it is impossible to fix the code as it is, we need a new one.
> ANY HELP IS VERY MUCH APPRECIATED.
> It doesn't have to mimic the current appender, quite the opposite. Maybe we should look over to log4j to see how they have structured things, maybe something completely different is needed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)