⚠java.util.logging improvements

• ⚠Upgrade dependencies. Most notably `org.slf:slf4-api:2.0.12)
• Bugfix: Set correct log level for java.util.logging.Loggers
• Improvement/bugfix: Avoid indirection through ConditionalLogEventGenerator when filter is Always or Never
• ⚠Removed HTTPS support to avoid recurring build problems with sun.security.x509 😢
• Adjustments for JsonLogEventFormatter and HttpServlet{Request,Response}MDC for easier override

bugfix: ConditionalLogEventGenerator.atLevel failed to filter with condition

logevents-parent-0.5.2

[maven-release-plugin] copy for tag logevents-parent-0.5.2

Add support for dynamic MDC with jakarta

logevents-parent-0.5.1

[maven-release-plugin] copy for tag logevents-parent-0.5.1

Support for org.slf4j.spi.LoggingEventBuilder

• Support LoggingEventBuilder: logger.atLevel(*level*).log(*message*)
• Support KeyValuePairs in JsonLogEventFormatter and PatternLogEventFormatte
• New Feature: Dynamic MDC: Allows for customization of JSON messages and for dynamically calculate MDC values
• ⚠Upgrade dependencies

FileLogEventObserver.filter and Elastic Common Schema support

• observer.file.threshold=WARN,INFO@mdc:foo=bar (hat tip @norrs )
• JsonLogEventFormatter confirms to Elastic Common Schema (ECS) structure (work-in-progress)

BUGFIX: Support running on filesystem root

Logevents tries to calculate the application name from the current working directory. However, when executed from filesystem root ("/"), this results in a NullPointerException. This is for example the case when running in a container created from jib-maven-plugin

Support slf4j 2.0.3

logevents-parent-0.4.2

[maven-release-plugin] copy for tag logevents-parent-0.4.2

Housekeeping: upgrade sonatype plugin for releases

logevents-parent-0.4.1

[maven-release-plugin] copy for tag logevents-parent-0.4.1

JUnit 5 support

logevents-parent-0.4.0

[maven-release-plugin] copy for tag logevents-parent-0.4.0

observer.console.logFilenameForPackages

ConsoleLogEventFormatter has a new configuration to determine which packages you would like to have logged as filenames. This was the standard behavior for all classes before.

Logging with file names instead of logger name lets IntelliJ and Eclipse create clickable links from the filename in the log messages. But this only makes sense for your own source code.

By default, logFilenameForPackages is set to the package of your main class.

Additional:

• LogEventStatus logs configuration of updates to loggers' observers and filters at level debug