[ANNOUNCE] Apache Log4j-Audit 1.0.1 released

[Ralph Goers <rg...@apache.org>]

The Apache Log4j Audit team is pleased to announce the Log4j Audit 1.0.1 
release!

Apache Log4j Audit is a framework for performing audit logging using a 
predefined catalog of audit events. It provides a tool to create and 
edit audit events. It also provides a REST service to perform the 
logging so that non-Java applications can use a common auditing facility.

Release 1.0.1

Changes in this version include:

Fixed Bugs

• LOG4J2-2428: Use the AuditExceptionHandler for validation exceptions. 
Thanks to Andrei Ivanov.
• LOG4J2-2443: Fix inconsistencies in validation exceptions. Thanks to 
Andrei Ivanov.
• LOG4J2-2440: AuditEvents should provide some basic toString(). Thanks 
to Andrei Ivanov.
• LOG4J2-2429: Setting the exceptionHandler on the AuditEvent sets it as 
a ThreadContext variable. Thanks to Andrei Ivanov.
• LOG4J2-2421: Add verbose parameter to the Log4j audit Maven plugin. 
Thanks to Andrei Ivanov.
• LOG4J2-2421: AbstractEventLogger.logEvent doesn't check for missing 
required context attributes. Thanks to Andrei Ivanov.
• LOG4J2-2417: Better handling of optional properties. Thanks to Andrei 
Ivanov.
• LOG4J2-2420: RequestContextFilter logging cleanup. Thanks to Andrei 
Ivanov.
• LOG4J2-2442: Normalize the event names logged through 
AbstractEventLogger.logEvent. Thanks to Andrei Ivanov.
• LOG4J2-2431: Narrow the return type of getEvent. Thanks to Andrei Ivanov.

Apache Log4j Audit 1.0.1 requires a minimum of Java 8 to build and run.

The download links for the source and binary artifacts can be found at 
http://logging.apache.org/log4j-audit/latest/download.html.

For complete information on Apache Log4j Audit, including instructions 
on how to submit bug reports, patches, or suggestions for improvement, 
see the Apache Apache Log4j Audit website:

http://logging.apache.org/log4j-audit/latest/

Re: [ANNOUNCE] Apache Log4j-Audit 1.0.1 released

[sebb <se...@gmail.com>]

On Thu, 13 Dec 2018 at 18:55, Ralph Goers <rg...@apache.org> wrote:
>
> The Apache Log4j Audit team is pleased to announce the Log4j Audit 1.0.1 release!
>
> Apache Log4j Audit is a framework for performing audit logging using a predefined catalog of audit events. It provides a tool to create and edit audit events. It also provides a REST service to perform the logging so that non-Java applications can use a common auditing facility.
>
> Release 1.0.1
>
> Changes in this version include:
>
> Fixed Bugs
>
> • LOG4J2-2428: Use the AuditExceptionHandler for validation exceptions. Thanks to Andrei Ivanov.
> • LOG4J2-2443: Fix inconsistencies in validation exceptions. Thanks to Andrei Ivanov.
> • LOG4J2-2440: AuditEvents should provide some basic toString(). Thanks to Andrei Ivanov.
> • LOG4J2-2429: Setting the exceptionHandler on the AuditEvent sets it as a ThreadContext variable. Thanks to Andrei Ivanov.
> • LOG4J2-2421: Add verbose parameter to the Log4j audit Maven plugin. Thanks to Andrei Ivanov.
> • LOG4J2-2421: AbstractEventLogger.logEvent doesn't check for missing required context attributes. Thanks to Andrei Ivanov.
> • LOG4J2-2417: Better handling of optional properties. Thanks to Andrei Ivanov.
> • LOG4J2-2420: RequestContextFilter logging cleanup. Thanks to Andrei Ivanov.
> • LOG4J2-2442: Normalize the event names logged through AbstractEventLogger.logEvent. Thanks to Andrei Ivanov.
> • LOG4J2-2431: Narrow the return type of getEvent. Thanks to Andrei Ivanov.
>
> Apache Log4j Audit 1.0.1 requires a minimum of Java 8 to build and run.
>
> The download links for the source and binary artifacts can be found at http://logging.apache.org/log4j-audit/latest/download.html.
>
> For complete information on Apache Log4j Audit, including instructions on how to submit bug reports, patches, or suggestions for improvement, see the Apache Apache Log4j Audit website:
>
> http://logging.apache.org/log4j-audit/latest/

The above link does not work in the email that you sent.

This is because the original email was sent as both text and HTML, and
the HTML copy was different from the text copy. The link seen by the
end user may depend on their mail client.

Please stick to plain text mails for the announce e-mails in future.




>