[jira] [Updated] (LOG4J2-1198) Add support for custom rollover strategy
[ https://issues.apache.org/jira/browse/LOG4J2-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1198: Fix Version/s: (was: 2.8.2) > Add support for custom rollover strategy > > > Key: LOG4J2-1198 > URL: https://issues.apache.org/jira/browse/LOG4J2-1198 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.4.1 >Reporter: Remko Popma > > [DefaultRolloverStrategy|http://logging.apache.org/log4j/2.x/manual/appenders.html#DefaultRolloverStrategy] > has a very compact configuration, but as a trade-off has become a bit > monolithic. I find it difficult to unit test and maintain. > Continuing in the spirit of the work done for LOG4J2-435, I would like to > break out components for the different kinds of processing done by > DefaultRolloverStrategy so that they can be individually configured and > combined by users. Users would configure a CustomRolloverStrategy by > specifying nested actions that define what needs to be done during a rollover. > The DefaultRolloverStrategy would still continue to work as current, but > under the hood can delegate to these components. > _At this stage the above is still just a concept. The description is to be > updated when it becomes more clear if and how this would work._ -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Updated] (LOG4J2-1198) Add support for custom rollover strategy
[ https://issues.apache.org/jira/browse/LOG4J2-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1198: Fix Version/s: (was: 2.8.1) 2.8.2 > Add support for custom rollover strategy > > > Key: LOG4J2-1198 > URL: https://issues.apache.org/jira/browse/LOG4J2-1198 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.4.1 >Reporter: Remko Popma > Fix For: 2.8.2 > > > [DefaultRolloverStrategy|http://logging.apache.org/log4j/2.x/manual/appenders.html#DefaultRolloverStrategy] > has a very compact configuration, but as a trade-off has become a bit > monolithic. I find it difficult to unit test and maintain. > Continuing in the spirit of the work done for LOG4J2-435, I would like to > break out components for the different kinds of processing done by > DefaultRolloverStrategy so that they can be individually configured and > combined by users. Users would configure a CustomRolloverStrategy by > specifying nested actions that define what needs to be done during a rollover. > The DefaultRolloverStrategy would still continue to work as current, but > under the hood can delegate to these components. > _At this stage the above is still just a concept. The description is to be > updated when it becomes more clear if and how this would work._ -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Updated] (LOG4J2-1198) Add support for custom rollover strategy
[ https://issues.apache.org/jira/browse/LOG4J2-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1198: Fix Version/s: (was: 2.8) 2.8.1 > Add support for custom rollover strategy > > > Key: LOG4J2-1198 > URL: https://issues.apache.org/jira/browse/LOG4J2-1198 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.4.1 >Reporter: Remko Popma > Fix For: 2.8.1 > > > [DefaultRolloverStrategy|http://logging.apache.org/log4j/2.x/manual/appenders.html#DefaultRolloverStrategy] > has a very compact configuration, but as a trade-off has become a bit > monolithic. I find it difficult to unit test and maintain. > Continuing in the spirit of the work done for LOG4J2-435, I would like to > break out components for the different kinds of processing done by > DefaultRolloverStrategy so that they can be individually configured and > combined by users. Users would configure a CustomRolloverStrategy by > specifying nested actions that define what needs to be done during a rollover. > The DefaultRolloverStrategy would still continue to work as current, but > under the hood can delegate to these components. > _At this stage the above is still just a concept. The description is to be > updated when it becomes more clear if and how this would work._ -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Updated] (LOG4J2-1198) Add support for custom rollover strategy
[ https://issues.apache.org/jira/browse/LOG4J2-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1198: Fix Version/s: (was: 2.7) 2.8 > Add support for custom rollover strategy > > > Key: LOG4J2-1198 > URL: https://issues.apache.org/jira/browse/LOG4J2-1198 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.4.1 >Reporter: Remko Popma > Fix For: 2.8 > > > [DefaultRolloverStrategy|http://logging.apache.org/log4j/2.x/manual/appenders.html#DefaultRolloverStrategy] > has a very compact configuration, but as a trade-off has become a bit > monolithic. I find it difficult to unit test and maintain. > Continuing in the spirit of the work done for LOG4J2-435, I would like to > break out components for the different kinds of processing done by > DefaultRolloverStrategy so that they can be individually configured and > combined by users. Users would configure a CustomRolloverStrategy by > specifying nested actions that define what needs to be done during a rollover. > The DefaultRolloverStrategy would still continue to work as current, but > under the hood can delegate to these components. > _At this stage the above is still just a concept. The description is to be > updated when it becomes more clear if and how this would work._ -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Updated] (LOG4J2-1198) Add support for custom rollover strategy
[ https://issues.apache.org/jira/browse/LOG4J2-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1198: Fix Version/s: (was: 2.6.1) 2.7 > Add support for custom rollover strategy > > > Key: LOG4J2-1198 > URL: https://issues.apache.org/jira/browse/LOG4J2-1198 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.4.1 >Reporter: Remko Popma > Fix For: 2.7 > > > [DefaultRolloverStrategy|http://logging.apache.org/log4j/2.x/manual/appenders.html#DefaultRolloverStrategy] > has a very compact configuration, but as a trade-off has become a bit > monolithic. I find it difficult to unit test and maintain. > Continuing in the spirit of the work done for LOG4J2-435, I would like to > break out components for the different kinds of processing done by > DefaultRolloverStrategy so that they can be individually configured and > combined by users. Users would configure a CustomRolloverStrategy by > specifying nested actions that define what needs to be done during a rollover. > The DefaultRolloverStrategy would still continue to work as current, but > under the hood can delegate to these components. > _At this stage the above is still just a concept. The description is to be > updated when it becomes more clear if and how this would work._ -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Updated] (LOG4J2-1198) Add support for custom rollover strategy
[ https://issues.apache.org/jira/browse/LOG4J2-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1198: - Fix Version/s: (was: 2.6) 2.6.1 > Add support for custom rollover strategy > > > Key: LOG4J2-1198 > URL: https://issues.apache.org/jira/browse/LOG4J2-1198 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.4.1 >Reporter: Remko Popma > Fix For: 2.6.1 > > > [DefaultRolloverStrategy|http://logging.apache.org/log4j/2.x/manual/appenders.html#DefaultRolloverStrategy] > has a very compact configuration, but as a trade-off has become a bit > monolithic. I find it difficult to unit test and maintain. > Continuing in the spirit of the work done for LOG4J2-435, I would like to > break out components for the different kinds of processing done by > DefaultRolloverStrategy so that they can be individually configured and > combined by users. Users would configure a CustomRolloverStrategy by > specifying nested actions that define what needs to be done during a rollover. > The DefaultRolloverStrategy would still continue to work as current, but > under the hood can delegate to these components. > _At this stage the above is still just a concept. The description is to be > updated when it becomes more clear if and how this would work._ -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Updated] (LOG4J2-1198) Add support for custom rollover strategy
[ https://issues.apache.org/jira/browse/LOG4J2-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1198: - Fix Version/s: (was: 2.5) 2.5.1 > Add support for custom rollover strategy > > > Key: LOG4J2-1198 > URL: https://issues.apache.org/jira/browse/LOG4J2-1198 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.4.1 >Reporter: Remko Popma > Fix For: 2.5.1 > > > [DefaultRolloverStrategy|http://logging.apache.org/log4j/2.x/manual/appenders.html#DefaultRolloverStrategy] > has a very compact configuration, but as a trade-off has become a bit > monolithic. I find it difficult to unit test and maintain. > Continuing in the spirit of the work done for LOG4J2-435, I would like to > break out components for the different kinds of processing done by > DefaultRolloverStrategy so that they can be individually configured and > combined by users. Users would configure a CustomRolloverStrategy by > specifying nested actions that define what needs to be done during a rollover. > The DefaultRolloverStrategy would still continue to work as current, but > under the hood can delegate to these components. > _At this stage the above is still just a concept. The description is to be > updated when it becomes more clear if and how this would work._ -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
