[
https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728550#comment-14728550
]
Remko Popma commented on LOG4J2-435:
------------------------------------
Thanks for the quick feedback!
ISO8601 looks interesting, thanks for the tip!
Perhaps a more generic name like simply <Delete> is better, especially given
Ralph's Schedule idea.
About the <Schedule> idea, I would like to support both:
* if the <Delete> element is nested in the <Policies> element (that is better,
yes) of a rolling appender it will activate on each rollover (in the calling
thread)
* when nested in a <Schedule> element it will run in the worker thread as
scheduled
Still to be fleshed out:
* how to specify multiple directories
* how to specify files in subdirectories (at any depth) of the base directory
Perhaps we can -steal some ideas from- be inspired by Ant's
[Selectors|https://ant.apache.org/manual/Types/selectors.html].
> Support limiting number of log files based on date pattern
> ----------------------------------------------------------
>
> Key: LOG4J2-435
> URL: https://issues.apache.org/jira/browse/LOG4J2-435
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Arkin Yetis
> Assignee: Ralph Goers
> Labels: Rollover
> Attachments: LimitingRolloverStrategy.java, SizeParser.java
>
>
> DefaultRolloverStrategy max attribute only applies if you have a %i in the
> file pattern. This request is to enhance DefaultRolloverStrategy or another
> appropriate component to allow a max number of files limit to apply across
> days/months/years when a filePattern includes a date pattern.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
