You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2022/10/07 04:21:00 UTC

[jira] [Commented] (LOG4J2-3615) Fix Log4j API OSGI encapsulation problem

    [ https://issues.apache.org/jira/browse/LOG4J2-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17613857#comment-17613857 ] 

Ralph Goers commented on LOG4J2-3615:
-------------------------------------

I don't think that should be a problem. However, it is a bigger problem to me that the code expects it to be a DefaultLogBuilder. We really should be using ServiceLoader to find a factory to create the LogBuilder implementation so users can provide their own if needed.

> Fix Log4j API OSGI encapsulation problem
> ----------------------------------------
>
>                 Key: LOG4J2-3615
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3615
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: API
>            Reporter: Piotr Karwasz
>            Priority: Minor
>
> The protected {{AbstractLogger.logBuilder}} field leaks the internal {{DefaultLogBuilder}} class into the public API.
> The field was introduced in August 2019, so switching it to private will be a breaking change.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)