Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 95760 invoked from network); 30 Sep 2010 06:49:46 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 Sep 2010 06:49:46 -0000 Received: (qmail 7468 invoked by uid 500); 30 Sep 2010 06:49:46 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 7061 invoked by uid 500); 30 Sep 2010 06:49:44 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 7052 invoked by uid 99); 30 Sep 2010 06:49:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Sep 2010 06:49:43 +0000 X-ASF-Spam-Status: No, hits=4.4 required=10.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of littlee1032@gmail.com designates 209.85.213.49 as permitted sender) Received: from [209.85.213.49] (HELO mail-yw0-f49.google.com) (209.85.213.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Sep 2010 06:49:36 +0000 Received: by ywi4 with SMTP id 4so711521ywi.36 for ; Wed, 29 Sep 2010 23:49:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=8sB18RPYOZm+aeMNG2IVsNRaAC2UfS0PJLk+1v03viQ=; b=pNHFfltKMH11FfDoMcFkmc0NJKwHAr5CB8OTNoJm+Mxt/W+jcKOt0DO8ChhkXxOJ+i 4sYIbLayMc8rG9MveWeQ5RT5MeOD3bGXK3DUrjPyDBkeUDn8WvIZUquuUN7loosIkdPi ok90sFRk4o8aATP/eQ52clYDQk3mI2Mn6gZvk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=jUZCSBnosGEQZFrOt7O7vmtGaCIPL9GifM9+r+KUeiEw+2sfqvNnD1Iay0MKhfneht 3tgis2AdMUBGvbn7dfx1tWzHKg9ZYmMcEvu2Z0WwY4YLxscQXar7t+SIhkmgXdUcW8q/ Grc1Zpbr3SEy4stT3JLfTYjmpFkuqZx3QW9BY= MIME-Version: 1.0 Received: by 10.224.114.89 with SMTP id d25mr2149163qaq.132.1285829355872; Wed, 29 Sep 2010 23:49:15 -0700 (PDT) Received: by 10.150.98.8 with HTTP; Wed, 29 Sep 2010 23:49:15 -0700 (PDT) Date: Thu, 30 Sep 2010 14:49:15 +0800 Message-ID: Subject: [discuss][java6] About the commons-logging jar included in the xmlsec From: Charles Lee To: dev@harmony.apache.org Content-Type: multipart/alternative; boundary=000feaee5824ffa327049174791c --000feaee5824ffa327049174791c Content-Type: text/plain; charset=ISO-8859-1 Hi guys, Does anybody know why do we remain the commons-logging.jar in the xmlsec? I am asking about this because: 1. I have comment out the commons-logging.jar in the bootstrap-classpath and run all the testcase. No related failures occurred. (20002 test cases, 4 failures, 2 errors and 3 crashes). 2. The *commons-logging.jar* included in the xmlsec is not the latest one. I found follows in the MANIFEST.MF: * * *Extension-Name: org.apache.commons.logging* *Specification-Vendor: Apache Software Foundation* *Specification-Version: 1.0* *Implementation-Vendor: Apache Software Foundation* *Implementation-Version: 1.0.4* * * the latest commons-logging version is 1.1.1. And u can find the CHANGELOG here . I do care about the LOGGING-115 , because lots of hadoop unit test case fail on this issue. -- Yours sincerely, Charles Lee --000feaee5824ffa327049174791c--