Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 29504 invoked from network); 20 Jan 2006 09:58:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Jan 2006 09:58:31 -0000 Received: (qmail 64395 invoked by uid 500); 20 Jan 2006 09:58:27 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 64340 invoked by uid 500); 20 Jan 2006 09:58:27 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 64329 invoked by uid 99); 20 Jan 2006 09:58:27 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jan 2006 01:58:27 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [134.98.65.18] (HELO gateway.elsag.de) (134.98.65.18) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jan 2006 01:58:25 -0800 Received: from vwall.elsag.de by gateway.elsag.de via smtpd (for asf.osuosl.org [140.211.166.49]) with ESMTP; Fri, 20 Jan 2006 10:58:03 +0100 Received: from esmail ([192.168.2.88]) by vwall-vs.elsag.de with InterScan Messaging Security Suite; Fri, 20 Jan 2006 10:58:02 +0100 Received: from esmail by esmail via smtpd (for vwall.elsag.de [192.168.100.108]) with ESMTP; Fri, 20 Jan 2006 10:58:02 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [logging] release status Date: Fri, 20 Jan 2006 10:58:02 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [logging] release status Thread-Index: AcYdoRnqP4OGR+zJRFGuvkJuCz7CLQAAgM4A From: =?iso-8859-1?Q?J=F6rg_Schaible?= To: "Jakarta Commons Developers List" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Simon, Simon Kitching wrote on Friday, January 20, 2006 10:01 AM: [snip] > commons-logging doesn't use maven to build the jars (only the site). >=20 > basedir=3D"${build.home}/classes" > manifest=3D"${build.home}/conf/MANIFEST.MF"> > > > > > >=20 > The currently generated manifest is: >=20 > Manifest-Version: 1.0 > Ant-Version: Apache Ant 1.6.5 > Created-By: 1.5.0_04-b05 (Sun Microsystems Inc.) > Extension-Name: org.apache.commons.logging > Specification-Vendor: Apache Software Foundation > Specification-Version: 1.0 > Implementation-Vendor: Apache Software Foundation > Implementation-Version: 1.1 >=20 >=20 > Do you know if there's anything extra needed? Well, it just claims, that 1.1 is still compatible to 1.0 regarding API = and spec. Cannot say, if this is really true, you're the expert here :) = Possibly a clirr report against JCL-1.0 will tell. Otherwise it looks = good. You might add an (optional) Specification-Title though: Specification-Title: "Jakarta Commons Logging" - J=F6rg BTW: Can you still use the resulting jar with 1.3? Just because it was = build with 1.5 ... --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org