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 11:48:38 UTC

[jira] [Updated] (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:all-tabpanel ]

Stefan Bodewig updated LOG4NET-557:
-----------------------------------
    Description: 
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.

  was:
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 MICH 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.


> 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
>            Reporter: Stefan Bodewig
>
> 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)