[
https://issues.apache.org/jira/browse/LOG4J2-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607821#comment-17607821
]
Ralph Goers commented on LOG4J2-3603:
-------------------------------------
I don't really understand this issue. The LoggingSystem only applies to
SpringBoot, where Spring is building a full application for you. If you are not
using Spring Boot then Spring uses Apache Commons Logging, not
java.util.logging. We already support redirection for that.
What is this issue really proposing?
> Provide a lightweight alternative to Spring's LoggingSystem
> -----------------------------------------------------------
>
> Key: LOG4J2-3603
> URL: https://issues.apache.org/jira/browse/LOG4J2-3603
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Piotr Karwasz
> Priority: Major
>
> While Spring Boot's
> [AbstractLoggingSystem|https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/logging/AbstractLoggingSystem.html]
> gives a nice abstraction that allows to configure a logging system (backend
> + multiple APIs), applications that do not use Spring Boot might profit from
> a lightweight alternative.
> The DI system of the 3.x series should allow us to detect the logging backend
> present at runtime, configure the correct JUL redirection handler and provide
> a uniform configuration format for logger configuration. The format might
> actually be a subset of the Log4j2 configuration format.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
