[
https://issues.apache.org/jira/browse/LOGGING-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789517#comment-17789517
]
Piotr Karwasz commented on LOGGING-173:
---------------------------------------
For completeness' sake, users can still enable these backends explicitly by
setting the value of the property '{{{}org.apache.commons.logging.Log{}}}' to
the fully qualified name of the logger
('{{{}org.apache.commons.logging.impl.AvalonLogger{}}}' or
'{{{}org.apache.commons.logging.impl.LogKitLogger{}}}') in either Java's system
properties or a {{commons-logging.properties}} file on the classpath.
> 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)
