I was going to go modify our changelog page earlier today to allow for
permalinks to the websites for specific versions, but I discovered
that this is not possible due to the rewrite rules in place. For
example, https://logging.apache.org/log4cxx/0.12.0 goes to
https://logging.apache.org/log4cxx/l
I agree with Ralph here. My suggestion would be to publish this custom
appender as a separate F/OSS project first. It can certainly be contributed
back to Log4j at a later stage depending on its reception by the community.
On Thu, May 5, 2022 at 9:27 AM Ralph Goers
wrote:
> While useful I have c
How is that different than what it already does? Today we simply inspect the
file extension and compress using that method after rollover.
Ralph
> On May 5, 2022, at 9:47 AM, Priyanka Pardesi Ramachander
> wrote:
>
> Hi All,
>
> How about this approach instead?..
> -> A new Boolean config op
Hi All,
How about this approach instead?..
-> A new Boolean config option "fileCompression" for the
RollingFileAppender.
-> If true, the log is written to FileOutputStream (as usual).
-> And at the time of rollover, compress the file (as .gz, .zip, etc) and
delete the original file.
In case of any
While useful I have concerns as to what the state of the file would be if the
application dies. Also, is the file readable as it is being written? The
RollingAppenders are already overly complicated so I am reluctant to add new
features without doing something to simplify them.
Ralph
> On May
