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 bel
Minimal source releases can be made by using git archive on the tag and
signing/hashing the file. Then commit those to the release candidate repo.
On Wed, Jun 2, 2021 at 23:22 Ralph Goers wrote:
> Unfortunately, without a source zip or gz there is no release to approve.
>
> Ralph
>
> > On Jun 1,
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
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
wrote:
> Overview
>
> Liquibase 3.6 as well as 4.0 introduced API
