From dev-return-19318-archive-asf-public=cust-asf.ponee.io@manifoldcf.apache.org Tue Mar 5 13:55:56 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 67145180648 for ; Tue, 5 Mar 2019 14:55:55 +0100 (CET) Received: (qmail 70249 invoked by uid 500); 5 Mar 2019 13:55:54 -0000 Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@manifoldcf.apache.org Delivered-To: mailing list dev@manifoldcf.apache.org Received: (qmail 70237 invoked by uid 99); 5 Mar 2019 13:55:53 -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; Tue, 05 Mar 2019 13:55:53 +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 710E1182108 for ; Tue, 5 Mar 2019 13:55:53 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.799 X-Spam-Level: * X-Spam-Status: No, score=1.799 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id t6hBzrYW3j0k for ; Tue, 5 Mar 2019 13:55:51 +0000 (UTC) Received: from mail-wr1-f47.google.com (mail-wr1-f47.google.com [209.85.221.47]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 3386F5F4AE for ; Tue, 5 Mar 2019 13:55:51 +0000 (UTC) Received: by mail-wr1-f47.google.com with SMTP id w2so9548494wrt.11 for ; Tue, 05 Mar 2019 05:55:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Bqq5YfCLYSdBlEzKRkWVo7rAZi3EVyF/pu+GtTAeseM=; b=rj8V1KmMuPbEnVNkjxpg9DfG3kKxJ012zL5t6tbuZK3kA1UUdk2UdwQgP2UF549Kkz QTzBnWnYd6zaITY1D9jIj9EwZgQORttytwCvSmQ2oO4hgcJeJ3dXKbqbsWIEV2W6BK4l pGQwti5XfkabOvM21hVuoJbWvNmAzFzPNDd4dMK9W+0yRxo9CrqSOhADWUO5O5SysEKV Gyr4RvSwBhFTH+G+AArb54WmDl0jb4yz/cIgNHWadPq/vb1vJ//OJy1x2GMPYuNuLO7A Kbt5P7YUCR6Sy0KqwHtXkkkBsWKHXkf4cmC+dmbHvOOCg19vK+dhc1/N0wHKHUg4G8Xh CwuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Bqq5YfCLYSdBlEzKRkWVo7rAZi3EVyF/pu+GtTAeseM=; b=tnv6UI1KAcW+3JSTCko+4Bpqa0Oy8T4J00AuglJe66fqfEO/YaKeTMvA0II/ql4Oga mJsKezqm+tmmcXf4msTK4TpogkRYhE5gTjcxRWV3/NIvLQq5tHVP8nb75pVg++hmgOof ELPz0KQMrhxmc25DZamXvXT6DC+5cIh+CchfHD+UDBzHMCJJGSbUOa3O216JITBsU/0a JxpbvMRKRoSrc3+HRsixEqwqBO2EqZD+FrLpDicDPHX3E0ZhJ9OysGCrGE4UJc5FBjZi jNfYMH7RgIxerXoTMp33wO1nq/QLZ2b2uUGkdfdAnDJV1l4A3oUaFZErOWa0w6zOGsGx NOhg== X-Gm-Message-State: APjAAAXD+qHTlyIz2eH/tMI2IpQUbyOmuQoJvAFuEV8stloBKXKX+VtG DUXsfMxMU1wNgfLXJAJVWkRX+sI57rkADsAob3rmlA== X-Google-Smtp-Source: APXvYqx3s9LuPp+n8gBT5rseOrpmd3vPZ+fVUGWsDUiH2QsSD81BV/ASOun44l4vv6KfNjVbG6PFAHDtcGWxNqWR2p4= X-Received: by 2002:adf:e8c7:: with SMTP id k7mr16986303wrn.298.1551794149714; Tue, 05 Mar 2019 05:55:49 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Karl Wright Date: Tue, 5 Mar 2019 08:55:38 -0500 Message-ID: Subject: Re: Log Framework Zoo To: dev Content-Type: multipart/alternative; boundary="0000000000000eef6d0583593b29" --0000000000000eef6d0583593b29 Content-Type: text/plain; charset="UTF-8" Two years ago I moved the standard logger for all of ManifoldCF to log4j 2. This was a non-backwards-compatible change but it was forced on us because our downstream connector dependencies started to require it. However, there are still log4j 1.2 dependencies we cannot get rid of due to other packages (like Jetty and Zookeeper) that haven't yet upgraded. So they all have to coexist together. It was a major chunk of work getting everything to run after this was done. I would suggest being *very* careful about removing dependencies even if you think they're not doing anything. Thanks, Karl On Tue, Mar 5, 2019 at 8:43 AM Markus Schuch wrote: > Hi, > > currently we have > > > * log4j-1.2.17.jar (Log4j 1 API & Impl) > * log4j-1.2-api-2.4.1.jar (Log4j 1 API to Log4j 2 Adapter) > * log4j-api-2.4.1.jar (Log4j 2 API) > * log4j-core-2.4.1.jar (Log4j 2 Impl) > * commons-logging-1.2.jar (Commons Logging API) > * jcl-over-slf4j-1.7.25.jar (Replacement for Commons Logging with > SLF4j in the stomach) > * slf4j-api-1.7.25.jar (SLF4J API) > * slf4j-simple-1.7.25.jar (Simple SLF4J Impl) > > > on our Classpath. > > I see the following problems: > > * Having both log4j-1.2.x.jar and log4j-1.2-api-2.x.jar is kind of > classloader roulette since both JARs contain the log4j 1.2 API packages and > classes with different implementation > * The same goes for commons-logging and jcl-over-slf4j > * Log statements from SLF4J are logged with a different logger, that > everything else > > I would suggest to (without having tried to compile it) > > * remove log4j-1.2.17.jar > * remove commons-logging-1.2.jar > * remove slf4j-simple-1.7.25.jar > * add log4j-slf4j-impl-2.4.1.jar (as replacement for slf4j-simple) > > But may be there are other historic reasons for having all those JARs > around. > > Has somebody more insights on that? > > Many thanks in advance, > Markus > > > ________________________________ > > Pflichtangaben anzeigen< > http://www.deutschebahn.com/pflichtangaben/20190304> > > N?here Informationen zur Datenverarbeitung im DB-Konzern finden Sie hier: > http://www.deutschebahn.com/de/konzern/datenschutz > --0000000000000eef6d0583593b29--