Re: MongoDB, Cassandra, CouchDB, Liquibase, Flume

Since JPMS didn't really add anything useful for module versions, perhaps our repos outside the main one can indicate their minimum log4j-core/api versions via the standard OSGi manifest.mf attributes? On 17 January 2018 at 04:09, Mikael Ståldal wrote: > Well, that's a

Re: MongoDB, Cassandra, CouchDB, Liquibase, Flume

Well, that's a decision we have to make. So far, logging-log4j-plugins has not been released yet, so we are now free do decide how to do it. I guess that logging-log4j-plugins over time will contain a diverse set of appenders, layouts and other plugins for Log4j 2, each one in its own Maven

Re: MongoDB, Cassandra, CouchDB, Liquibase, Flume

And there is no obvious way to tell what matches to what :-( Gary On Tue, Jan 16, 2018 at 4:34 PM, Ralph Goers wrote: > Because logging-log4j-plugins is released separately from logging-log4j2 > and the versions would not line up. > > Ralph > > > On Jan 16, 2018, at

Re: MongoDB, Cassandra, CouchDB, Liquibase, Flume

Because logging-log4j-plugins is released separately from logging-log4j2 and the versions would not line up. Ralph > On Jan 16, 2018, at 2:31 PM, Mikael Ståldal wrote: > > Why do we need to change the version number? > > On 2018-01-14 22:11, Ralph Goers wrote: >> I don’t

Re: MongoDB, Cassandra, CouchDB, Liquibase, Flume

I originally developed log4j-liquibase. I have not used it or Liquibase itself for quite some time now. It might be so that the next version of Liquibase will make that module obsolete. But maybe we should keep it around at least until such new version of Liquibase is released? On

Re: MongoDB, Cassandra, CouchDB, Liquibase, Flume

Why do we need to change the version number? On 2018-01-14 22:11, Ralph Goers wrote: I don’t believe the components listed in the subject line should be part of the main flume build and would like to see them moved to the logging-log4j-plugins project. The only problem is that the modules and

Re: MongoDB, Cassandra, CouchDB, Liquibase, Flume

Using that would work, but if you want to just use Log4j 2 then you have to customize the logging classes in Liquibase. Ralph > On Jan 15, 2018, at 1:15 PM, Matt Sicker wrote: > > Oh in that case, it'd just be easier to use log4j-slf4j-impl, right? > > On 14 January 2018 at

Re: MongoDB, Cassandra, CouchDB, Liquibase, Flume

Oh in that case, it'd just be easier to use log4j-slf4j-impl, right? On 14 January 2018 at 22:51, Ralph Goers wrote: > You are correct. And after looking at the class and at Liquibase master > this code is now completely broken and should be dropped. 3.5.3 is the >

Re: MongoDB, Cassandra, CouchDB, Liquibase, Flume

You are correct. And after looking at the class and at Liquibase master this code is now completely broken and should be dropped. 3.5.3 is the latest Liquibase release and the code possibly still works with that, although the unit tests certainly don’t prove that. But the code in master has

Re: MongoDB, Cassandra, CouchDB, Liquibase, Flume

>From when I used log4j-liquibase in the past, it doesn't log _to_ liquibase; instead, it offers an implementation of its internal logger logic which doesn't use any existing facade by default. On 14 January 2018 at 17:14, Ralph Goers wrote: > Ok. > > If we do this

Re: MongoDB, Cassandra, CouchDB, Liquibase, Flume

Ok. If we do this we should release that before we remove them from a Log4J release to minimize confusion. Sent from my iPhone > On Jan 14, 2018, at 3:47 PM, Remko Popma wrote: > > No objection from me. > > Let’s make it a community goal to speed up the Log4j2 build.

Re: MongoDB, Cassandra, CouchDB, Liquibase, Flume

No objection from me. Let’s make it a community goal to speed up the Log4j2 build. We should start by creating a JIRA epic (it’s in maintenance now but when it’s back up). (Shameless plug) Every java main() method deserves http://picocli.info > On Jan 15, 2018, at 6:11, Ralph Goers

MongoDB, Cassandra, CouchDB, Liquibase, Flume

I don’t believe the components listed in the subject line should be part of the main flume build and would like to see them moved to the logging-log4j-plugins project. The only problem is that the modules and maven coordinates need to change since the version numbers will be going backwards. I