[slf4j-dev] [JIRA] Updates for SLF4J-588: User manual: Refers to [Apache] Commons Logging as "Jakarta Commons Logging"

slf4j developers list slf4j-dev at qos.ch
Tue May 2 18:09:00 CEST 2023


SLF4J / SLF4J-588 [Open]
User manual: Refers to [Apache] Commons Logging as "Jakarta Commons Logging"

==============================

Here's what changed in this issue in the last few minutes.

This issue has been created
This issue is now assigned to you.


View or comment on issue using this link
https://jira.qos.ch/browse/SLF4J-588

==============================
 Issue created
------------------------------

Philippe Cloutier created this issue on 02/May/23 18:00

Summary:              User manual: Refers to [Apache] Commons Logging as "Jakarta Commons Logging"
Issue Type:           Bug
Assignee:             SLF4J developers list
Created:              02/May/23 18:00
Priority:             Trivial
Reporter:             Philippe Cloutier
Description:
  The user manual refers to [Commons-logging|https://commons.apache.org/proper/commons-logging/] twice in [its Binding with a logging framework at deployment time section|https://www.slf4j.org/manual.html#swapping], most importantly in its description of slf4j-jcl-2.0.7.jar:
  ??Binding/provider for Jakarta Commons Logging. This binding will delegate all SLF4J logging to JCL.??
  
  While calling Commons Logging "Jakarta Commons Logging" may not be incorrect, it would be much better to call it "Apache Commons Logging", since [it was renamed|https://bugzilla.redhat.com/show_bug.cgi?id=589168] more than 13 years ago.
  
  Note that despite this rename, the previous acronym "JCL" is strangely still used, so I would suggest to keep mentioning "Jakarta Commons Logging" or at least keep the acronym.


==============================
 This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)



More information about the slf4j-dev mailing list