[jira] [Commented] (LOG4J2-3418) Proper registration of Log4j2CloudConfigLoggingSystem

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on LOG4J2-3418:
---------------------------------------------------------

Commit 48ab5e97e52a35676a90742732b247d1efb2f374 in logging-log4j2's branch refs/heads/release-2.x from Piotr P. Karwasz
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=48ab5e9 ]

[LOG4J2-3418] Fix Log4j2CloudConfigLoggingSystem registration

This PR adds support for the `spring.factories` registration method of
the `Log4j2CloudConfigLoggingSystem` to replace the old Java system
properties injection method.

A Log4j 2.x `log4j2.disableCloudConfigLoggingSystem` property is added
to enable a choice between the `Log4j2CloudConfigLoggingSystem` and
`Log4j2LoggingSystem`.

> Proper registration of Log4j2CloudConfigLoggingSystem
> -----------------------------------------------------
>
>                 Key: LOG4J2-3418
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3418
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Spring
>    Affects Versions: 2.14.0
>            Reporter: Piotr P. Karwasz
>            Priority: Major
>
> The current version of {{log4j-spring-boot}} sets Java's {{org.springframework.boot.logging.LoggingSystem}} property to force the usage of the {{Log4j2CloudConfigLoggingSystem}}.
> This can potentially break applications running in the same JVM, if they use different logging systems.
> The artifact should use the {{spring.factories}} detection mechanism instead.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)