Releases: kumuluz/kumuluzee-logs
v1.4.6
v1.4.5
This patch release updates the log4j dependency to 2.17.0. This version of log4j2 fixes the latest log4j CVE-2021-45105, which might cause DOS with certain logging configurations. For more information see: https://logging.apache.org/log4j/2.x/security.html
Enhancements
- Upped log4j dependency to 2.17.0
v1.4.4
This patch release updates the log4j dependency to 2.16.0. This version of log4j2 disables JNDI lookups by default. For more information about this log4j2 update and how it relates to the recent CVE, see the log4j 2.16.0 release notes: https://lists.apache.org/thread/d6v4r6nosxysyq9rvnr779336yf0woz4
Enhancements
- Upped log4j dependency to 2.16.0
v1.4.3
This patch release updates the log4j2 dependency to 2.15.0, which fixes CVE-2021-44228.
Enhancements
- Upped log4j dependency to 2.15.0
v1.4.2
v1.4.1
This quick release includes a fix that skips context logging in cases where EeConfig is not initialised and adds a method for retrieving Logger instances.
Enhancements
- Added a method for retrieving a Logger instance.
Bugs
- Skip context logging if EeConfig is not initialized.
v1.4.0
We're announcing the availability of KumuluzEE Logs 1.4.0, which introduces two big features; support for Fluentd logging provider and an audit logging module.
Features
- Fluentd is now supported as a logging provider.
- An audit logging module provides features for logging the audit trail using the supported logging frameworks.
- Logging context can now be added to logs by implementing the
RequestContext
interface.
v1.3.1
v1.3.0
We're announcing the availability of KumuluzEE Logs 1.3.0.
This release includes support for KumuluzEE version 2.4.0 and a new implementation of the logging extensions Java Util Logging
. Although the new version is backward compatible with your code it was completely reorganised as part of the major reorganisation that was developed in tandem withe the core KumuluzEE
framework. This does however mean that this version required KumuluzEE 2.4.0 or higher in order to work. All the extra logging functionality was moved here (LogCommons
, Logger
, ...) and will now be available when adding any of the implementations to your project.
We're also adding support for basic common configuration (config file, log levels, ...) via the configuration framework that will be applied to whichever underlying implementation you choose. This allows you to configure logging alongside everything else in the framework and keep the configuration implementation independent.
Features
- Reorganised to work with the latest version of the KumuluzEE logging extensions.
- All the extra logging functionality (
LogCommons
etc.) that was previously available in the KumuluzEE core module was moved here, to better follow the modularity approach we are going for. - New logging extensions implementation - Java Util Logging.
- Support for basic common configuration through the configuration framework.
Enhancements
- (log4j2) Automatic configuration of the JUL bridge.
- (log4j2) Added commons-logging bridge.
v1.2.0
We're announcing the availability of KumuluzEE Logs 1.2.0.
This release is relatively small update that includes the updated extension implementation found in KumuluzEE version 2.3.0, as such this version requires that you use KumuluzEE version 2.3.0 or later and is not compatible with older versions. We're also bundling the SLF4J and JUL bridges for the LOG4j2 implementation so you have everything ready to route all your logging into LOG4j2.
Features
- Added the SLF4J and JUL bridge to LOG4j2.
Enhancements
- Added the disruptor dependency to LOG4j2 to enable asynhroneous logging