[
https://issues.apache.org/jira/browse/LOGGING-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811358#comment-17811358
]
Elliotte Rusty Harold commented on LOGGING-187:
-----------------------------------------------
The title of this issue is confusing. If it's correct, then that's done. That
is, there is a 1.3 release. If this is about releasing 2.0 we should change the
title.
That said, I agree with the sentiment here. Apache Commons Logging 1.x is a
huge source of dependency problems thanks to very outdated logging frameworks.
Now that 1.3 is out, I think we should release 2.0 soonish with the following
changes:
* 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)
* Update or remove other dependencies as possible
However I don't think we should change the group ID or package names, and I
don't think we should require Java 11 yet. The community needs a Java 8
supporting commons-logging that is a drop-in replacement for everyone who isn't
using unsupported and two decade old logging frameworks.
Otherwise I don't want to break API compatibility in this release. Maybe
they're a few deprecated bits here and there no one is using that can also be
cleaned up — e.g. default constructors in utility classes or other trivia — but
mostly I just want a version of exactly what we have now that works better with
2024 classpaths.
> 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)
