Yeah - I have proposed moving all these extra integrations to a separate repo but I’ve never gotten consensus. I’d prefer to have a project like log4j-pubsub where things like JMS, JeroMQ, etc can go live, log4j-nosql for all the nosql modules, etc. The problem seems to be that some people believe that we would have to cut a release of those every time we do a log4j release.
If we were to do that 3.0 would be the right time. Ralph > On Jun 3, 2021, at 7:46 AM, Matt Sicker <boa...@gmail.com> wrote: > > It was probably contributed as a logging bridge/adapter similar to the > SLF4J, JCL, JUL, etc, modules. Normally I’d say that this is the > appropriate place to add anything related to log4j, but there are so many > customizations out in the wild (see for instance the Spring Boot > initialization stuff), I can’t exactly say that it’s always the best idea. > > On Thu, Jun 3, 2021 at 08:21 Volkan Yazıcı <volkan.yaz...@gmail.com> wrote: > >> I am just curious, why is the Liquibase logger a part of the Log4j project? >> Shouldn't Liquibase itself be providing the logging bridges of their >> software for certain logging backends? >> >> On Wed, Jun 2, 2021 at 10:17 PM Nathan Voxland <notificati...@github.com> >> wrote: >> >>> Overview >>> >>> Liquibase 3.6 as well as 4.0 introduced API compatibility issues with the >>> current log4j-liquibase codebase. See liquibase/liquibase#1777 >>> <https://github.com/liquibase/liquibase/issues/1777> >>> >>> This updates the code to be compatible with 4.0+ while still supporting >>> 3.5 and 3.6+ users. >>> ------------------------------ >>> You can view, comment on, or merge this pull request online at: >>> >>> https://github.com/apache/logging-log4j2/pull/503 >>> Commit Summary >>> >>> - Updated log4j-liquibase to be compatible with both 3.x and 4.x >>> versions of Liquibase >>> - Updated log4j-liquibase to be compatible with both 3.x and 4.x >>> versions of Liquibase >>> >>> File Changes >>> >>> - *A* >>> >> log4j-liquibase/src/main/java/liquibase/ext/logging/log4j2/DeprecatedLog4j2Logger.java >>> < >> https://github.com/apache/logging-log4j2/pull/503/files#diff-aabadf00cbeee77ba36f78292fe7dc11fe16c3b46f2a8b64b93c219514fec86b >>> >>> (189) >>> - *M* >>> >> log4j-liquibase/src/main/java/liquibase/ext/logging/log4j2/Log4j2Logger.java >>> < >> https://github.com/apache/logging-log4j2/pull/503/files#diff-a3fb75cc20998f82ba5cb4783d5f57420eead2d5277b6007b8f23554fd25c714 >>> >>> (157) >>> - *A* >>> >> log4j-liquibase/src/main/java/liquibase/ext/logging/log4j2/Log4j2LoggerService.java >>> < >> https://github.com/apache/logging-log4j2/pull/503/files#diff-62b7869399bb7251582033dd21d08acc257f56e3cd6bd426bc68e92f67e0ab11 >>> >>> (47) >>> - *A* >>> >> log4j-liquibase/src/main/resources/META-INF/services/liquibase.logging.LogService >>> < >> https://github.com/apache/logging-log4j2/pull/503/files#diff-41f6a06104e2662ac0882a53045eb884cd5b9009d1e5de8e847e04b2aa79ac2b >>> >>> (1) >>> - *R* >>> >> log4j-liquibase/src/test/java/liquibase/ext/logging/log4j2/DeprecatedLog4J2LoggerTest.java >>> < >> https://github.com/apache/logging-log4j2/pull/503/files#diff-7b353543266b0e9219b856fac1c3df928764f8a41612e5e59ea3841b75e11d3e >>> >>> (8) >>> - *A* >>> >> log4j-liquibase/src/test/java/liquibase/ext/logging/log4j2/Log4j2LoggerTest.java >>> < >> https://github.com/apache/logging-log4j2/pull/503/files#diff-ae83836593517181c94282dfacab38f16e1741fa3503c1c4a5297753efe4e09d >>> >>> (86) >>> - *M* pom.xml >>> < >> https://github.com/apache/logging-log4j2/pull/503/files#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8 >>> >>> (3) >>> >>> Patch Links: >>> >>> - https://github.com/apache/logging-log4j2/pull/503.patch >>> - https://github.com/apache/logging-log4j2/pull/503.diff >>> >>> — >>> You are receiving this because you are subscribed to this thread. >>> Reply to this email directly, view it on GitHub >>> <https://github.com/apache/logging-log4j2/pull/503>, or unsubscribe >>> < >> https://github.com/notifications/unsubscribe-auth/AAARTSNWLZC4VTOBYVGT4TTTQ2GT3ANCNFSM457M3ARA >>> >>> . >>> >>
