[
https://issues.apache.org/jira/browse/LOGGING-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789504#comment-17789504
]
Piotr Karwasz commented on LOGGING-187:
---------------------------------------
[~ggregory],
I am referring to the upgrade from 1.2 to 1.3.
However I forgot one category of users: those that forward both JCL and SLF4J
to Log4j 1.x. Those users should also not be affected if we disable
{{Log4JLogger}} by default. I think that these days having a dependency stack
that does not include SLF4J must be *very* rare. So we can disable Avalon,
Lumberjack and even Log4j 1.x by default and only describe how to enable them
back in a Jira ticket.
> release current state of master as 1.3
> --------------------------------------
>
> Key: LOGGING-187
> URL: https://issues.apache.org/jira/browse/LOGGING-187
> Project: Commons Logging
> Issue Type: Task
> Reporter: Samael Bate
> Priority: Major
>
> master branch appears to be in a good state. Please can someone within Apache
> tag/publish a new release so that the following changes can be made as a v2:
> * Remove Avalon & Lumberjack loggers
> (https://issues.apache.org/jira/browse/LOGGING-173)
> * Replace log4j 1 with log4j 2
> (https://issues.apache.org/jira/browse/LOGGING-180,
> https://issues.apache.org/jira/browse/LOGGING-181)
> * Change _GroupId_ of maven artifact to *org.apache.commons* like other
> Apache Commons libs.
> * Potentially bump the minimum support JDK (v11 will be needed for recent
> logback)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
