Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Date: Sun, 18 Sep 2016 10:53:20 +0000 (UTC)
From: "Remko Popma (JIRA)" <jira@apache.org>
To: log4j-dev@logging.apache.org
Message-ID: <JIRA.12913151.1447596472000.599342.1474196000905@Atlassian.JIRA>
In-Reply-To: <JIRA.12913151.1447596472000@Atlassian.JIRA>
References: <JIRA.12913151.1447596472000@Atlassian.JIRA> <JIRA.12913151.1447596472727@arcas>
Subject: [jira] [Updated] (LOG4J2-1198) Add support for custom rollover
 strategy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 18 Sep 2016 10:53:22 -0000


     [ 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-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org