The actions originated with the Log4j1 extended design and code. I started from
that and then tried to merge the rollover strategies into something that made
sense to me. That doesn't mean it can't be changed.
Sent from my iPad
> On Feb 2, 2014, at 12:11 AM, Remko Popma wrote:
>
> Yes, I was
On Monday, February 3, 2014, Gary Gregory wrote:
> On Sun, Feb 2, 2014 at 3:11 AM, Remko Popma
> >
> wrote:
>
> > Yes, I was thinking along similar lines.
> >
> > Something like https://issues.apache.org/jira/browse/LOG4J2-491
> > but perhaps more general.
> >
> > I haven't got it all worked out
On Sun, Feb 2, 2014 at 3:11 AM, Remko Popma wrote:
> Yes, I was thinking along similar lines.
>
> Something like https://issues.apache.org/jira/browse/LOG4J2-491
> but perhaps more general.
>
> I haven't got it all worked out yet but I find the current
> DefaultRolloverStrategy difficult to unit-
Hi all,
please show your support for your favorite logo on this wiki page:
http://wiki.apache.org/logging/Log4jLogoNominations
I added a few nominations already, just stick with the format.
Everybody reading this message is invited to nominate their favorite logo.
Cheers,
Christian
---
Yes, I was thinking along similar lines.
Something like https://issues.apache.org/jira/browse/LOG4J2-491
but perhaps more general.
I haven't got it all worked out yet but I find the current
DefaultRolloverStrategy difficult to unit-test. E.g., file deletes are not
actions, but renaming and zippin
