[
https://issues.apache.org/jira/browse/LOGGING-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789668#comment-17789668
]
Gary D. Gregory commented on LOGGING-173:
-----------------------------------------
The plan (or at least mine) is not breaking binary compatibility in the
upcoming 1.3.0 release ;) So NOTHING will be removed. Any breaking of BC will
have to be for a future 2.0 with the usual mechanics for a new major release.
There are a few more PRs from [~pkarwasz] to handle for 1.3.0 so I should be
able to cut a release candidate very soon.
> Shall we remove AvalonLogger and LogKitLogger?
> ----------------------------------------------
>
> Key: LOGGING-173
> URL: https://issues.apache.org/jira/browse/LOGGING-173
> Project: Commons Logging
> Issue Type: Improvement
> Reporter: Tomo Suzuki
> Priority: Minor
>
> Do you think it's good idea to move
> org.apache.commons.logging.impl.AvalonLogger and
> org.apache.commons.logging.impl.LogKitLogger from commons-logging? (logkit is
> part of the Avalon project)
> I see Apache Avalon project closed in 2004.
> https://avalon.apache.org/closed.html
> (I'm not suffering from these classes. I found these classes while
> [investigating class references using our
> tool|https://github.com/GoogleCloudPlatform/cloud-opensource-java/issues/1871]
> and saw the Avalon project has been closed a while ago. I thought it's a
> good idea to share the finding here)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
