From dev-return-5405-apmail-logging-dev-archive=logging.apache.org@logging.apache.org Thu Jan 11 05:04:34 2018 Return-Path: X-Original-To: apmail-logging-dev-archive@minotaur.apache.org Delivered-To: apmail-logging-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B0CBF1772D for ; Thu, 11 Jan 2018 05:04:34 +0000 (UTC) Received: (qmail 86575 invoked by uid 500); 11 Jan 2018 05:04:34 -0000 Delivered-To: apmail-logging-dev-archive@logging.apache.org Received: (qmail 86520 invoked by uid 500); 11 Jan 2018 05:04:34 -0000 Mailing-List: contact dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@logging.apache.org Delivered-To: mailing list dev@logging.apache.org Received: (qmail 86509 invoked by uid 99); 11 Jan 2018 05:04:34 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Jan 2018 05:04:34 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 73B2D180782 for ; Thu, 11 Jan 2018 05:04:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.05 X-Spam-Level: X-Spam-Status: No, score=0.05 tagged_above=-999 required=6.31 tests=[KAM_INFOUSMEBIZ=0.75, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id amP-3KKdCohD for ; Thu, 11 Jan 2018 05:04:28 +0000 (UTC) Received: from smtp618.redcondor.net (smtp618.redcondor.net [208.80.206.18]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 3A6E45F250 for ; Thu, 11 Jan 2018 05:04:28 +0000 (UTC) Received: from mailproxy10.neonova.net ([137.118.22.75]) by smtp618.redcondor.net ({25934d7d-0c4d-4838-a484-2a3cc0768185}) via TCP (outbound) with ESMTP id 20180111050420041_0618 for ; Thu, 11 Jan 2018 05:04:20 +0000 X-RC-FROM: X-RC-RCPT: Received: from [172.20.3.84] (24-156-92-46.sdoncmtk01.com.sta.suddenlink.net [24.156.92.46]) (Authenticated sender: ralph.goers@dslextreme.com) by mailproxy10.neonova.net (Postfix) with ESMTPA id C36B5360591 for ; Thu, 11 Jan 2018 00:04:15 -0500 (EST) From: Ralph Goers Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: [log4j] MongoDB Appender changes heads up. Date: Wed, 10 Jan 2018 22:04:14 -0700 References: <535A91BA-98C3-40C6-A7B0-BFA07D4F4290@gmail.com> To: dev@logging.apache.org In-Reply-To: Message-Id: <3FF4E4BE-09F1-415F-8C20-DBEA2FD74719@dslextreme.com> X-Mailer: Apple Mail (2.3445.5.20) X-DLP-OUTBOUND: 137.118.22.64/27 X-MAG-OUTBOUND: greymail.redcondor.net@137.118.22.64/27 So now we need Java 7, 8 and 9 to perform a build? Did you update the = build documentation? Is that the only tool available to test MongoDB? Ralph > On Jan 10, 2018, at 8:18 PM, Gary Gregory = wrote: >=20 > The changes are both binary compatible and behavior compatible. The = new > code kicks in only if the NoSqlAppender node contains a MessageLayout > child, which was not possible before. >=20 > I also added some code to test against an embedded MongoDB instance by > using code from de.flapdoodle.embed.mongo. This all works from Eclipse = and > from my Windows command line but Jenkins is having some trouble it = seems. >=20 > The code from de.flapdoodle.embed.mongo requires Java 8 so I am using = a > special JUnit test suite to run the code with a JUnit Assume that only = runs > the suite on Java 8 and above. >=20 > But for some reason, when Jenkins compiles the MongoDB tests it = complains > about byte code versions 52 vs. 51. It might be the case that the = MongoDB > tests will need to be compiled with Java 8. Not sure yet... >=20 > Gary >=20 > On Wed, Jan 10, 2018 at 5:22 PM, Remko Popma = wrote: >=20 >> No objection, but please do this in a way that existing users of this >> appender are not affected. >>=20 >> So if the new behavior is incompatible with the current behavior, = then the >> new behavior should be switched on explicitly in configuration. >>=20 >> Remko >>=20 >> (Shameless plug) Every java main() method deserves = http://picocli.info >>=20 >>> On Jan 11, 2018, at 7:49, Gary Gregory = wrote: >>>=20 >>> Hi All: >>>=20 >>> I need for the MongoDB Appender to behave similarly to the JMS = Appender >>> regarding MapMessages. >>>=20 >>> What I plan on doing: >>>=20 >>> Like with the JMS Appender, if the MongoDB element contains a child >>> MessageLayout element, the MongoDB appender will apply this layout. >>>=20 >>> Like with the JMS Appender, my goal is to let a MapMessage be = converted >> to >>> a MongbDB object with key and values from the MapMessage, not from = the >>> LogEvent. >>>=20 >>> I will create a Jira. >>>=20 >>> Gary >>=20