Re: StatusLogger contention?

So any thoughts on how the output got garbled in a Maven build? I wonder if Maven 3.5.4 introduced a bug? Gary On Tue, Jun 26, 2018, 15:47 Ralph Goers wrote: > No. > > Ralph > > > On Jun 26, 2018, at 12:18 PM, Gary Gregory > wrote: > > > > Hi All: > > > > I get this garbled StatusLogger output

Re: Log4j Kotlin adapter

I committed the changes to get the web site building. Have fun. Ralph > On Jun 4, 2018, at 8:38 AM, Matt Sicker wrote: > > I'm in the process of moving, but after that's all settled, I'll have more > time to work on this more. > > On 4 June 2018 at 00:46, Ralph Goers wrote: > >> Just more t

Re: StatusLogger contention?

No. Ralph > On Jun 26, 2018, at 12:18 PM, Gary Gregory wrote: > > Hi All: > > I get this garbled StatusLogger output when running Mongo tests from Maven: > > [INFO] Running org.apache.logging.log4j.mongodb3.MongoDbMapMessageTest > ERREERORRROOR StatusLogger No Log4j 2 configuration file founR

Fwd: StatusLogger contention?

Hi All: I get this garbled StatusLogger output when running Mongo tests from Maven: [INFO] Running org.apache.logging.log4j.mongodb3.MongoDbMapMessageTest ERREERORRROOR StatusLogger No Log4j 2 configuration file founRd. UsingR defau StatusLogger No Log4j 2 configuration file found.lt configuratio