Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 82836 invoked from network); 4 Oct 2006 19:53:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Oct 2006 19:53:00 -0000 Received: (qmail 73719 invoked by uid 500); 4 Oct 2006 19:52:55 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 73678 invoked by uid 500); 4 Oct 2006 19:52:55 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 73667 invoked by uid 99); 4 Oct 2006 19:52:55 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Oct 2006 12:52:55 -0700 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests= Received: from [212.27.42.30] ([212.27.42.30:51850] helo=smtp4-g19.free.fr) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id 42/92-20288-41114254 for ; Wed, 04 Oct 2006 12:52:54 -0700 Received: from [192.168.0.1] (gou06-1-82-224-99-120.fbx.proxad.net [82.224.99.120]) by smtp4-g19.free.fr (Postfix) with ESMTP id D2EE554864 for ; Wed, 4 Oct 2006 21:52:49 +0200 (CEST) Message-ID: <45241112.9020907@apache.org> Date: Wed, 04 Oct 2006 21:52:50 +0200 From: Remy Maucherat User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: Package renaming References: <4523CFFE.7020708@apache.org> <1159982949.2337.14.camel@wlt.obsidian-studios.com> In-Reply-To: <1159982949.2337.14.camel@wlt.obsidian-studios.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N William L. Thomson Jr. wrote: > I have no foreseeable solution to building that jar on Gentoo at this > time. I have discussed it extensively with others, and we are likely to > have to do some package specific hacks or etc to build that jar. In the > mean time, those needing that jar are having to fetch it from the a > binary release. Ok, but you don't really have to care that much about that JAR: Tomcat is still perfectly usable using the regular commons-dbcp, etc. It's not the same situation here, so you won't run into any problem. An implementation of commons-logging (I thought the one Costin did in tomcat-lite could be reasonable to start with) would be included in the Tomcat source and built along with the rest. R�my --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org