[
https://issues.apache.org/jira/browse/JCS-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937886#comment-17937886
]
Gary D. Gregory commented on JCS-241:
-------------------------------------
bq. > What kind of incompatibilities?
bq. Loads of removed deprecated code, for example.
So you're saying that git master currently breaks binary compatibility? That's
fine for 4.0 but I want to make sure I understand.
> Use System.Logger abstraction
> -----------------------------
>
> Key: JCS-241
> URL: https://issues.apache.org/jira/browse/JCS-241
> Project: Commons JCS
> Issue Type: Improvement
> Reporter: Piotr Karwasz
> Assignee: Piotr Karwasz
> Priority: Minor
> Fix For: jcs-4.0
>
>
> Commons JCS contains a logging wrapper in {{o.a.c.jcs3.log}}.
> Using a logging wrapper causes several issues:
> * Users need to set the hard to find {{jcs.logSystem}} system property to
> switch between the JUL and Log4j API backend.
> * Both backends lose location information, which will always point to the
> wrapper class as source of all log events.
> For this reason I propose to:
> * Rewrite Commons JCS to use the System.Logger API directly.
> * Deprecate the logging wrapper and related methods (e.g.
> {{JCS.setLogSystem}}) for removal in the next major version.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
