[ARTEMIS-4020] switch to using SLF4J for logging API and use Log4j 2 for broker distribution - ASF JIRA

Rank to Top

Rank to Bottom

Bulk Copy Attachments

Bulk Move Attachments

Voters

Watch issue

Watchers

Convert to sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 2.27.0
Component/s: None
Labels:
None

Description

Switch to using SLF4J as the logging API for the code base, with end-uses supplying and configuring an SLF4J-supporting logging implementation of their choice based on their needs.

For the client, applications will need to supply an SLF4J binding to a logging implementation of their choice to enable logging. An example of doing so using Log4J 2 is given in (/will be, once the release is out) the client logging documentation.

For the broker, the assembly distribution will include Log4J 2 as its logging implentation, with the "artemis create" CLI command used to create broker instances now creating a log4j2.properties configuration within the <broker-instance>/etc/ directory to configure Log4J. Details for upgrading an existing broker-instance is given in (/will be, once the release is out) the version upgrade documentation.