Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 95986 invoked from network); 9 Jan 2002 18:29:10 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 9 Jan 2002 18:29:10 -0000 Received: (qmail 5768 invoked by uid 97); 9 Jan 2002 18:29:11 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 5752 invoked by uid 97); 9 Jan 2002 18:29:10 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: 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 5741 invoked from network); 9 Jan 2002 18:29:10 -0000 Date: Wed, 9 Jan 2002 18:30:08 +0000 Subject: Re: [Logging] A few unresolved issues Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v475) From: robert burrell donkin To: "Jakarta Commons Developers List" Content-Transfer-Encoding: 7bit In-Reply-To: <20020108140600.I12403-100000@icarus.apache.org> Message-Id: X-Mailer: Apple Mail (2.475) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tuesday, January 8, 2002, at 10:08 PM, Craig R. McClanahan wrote: > In fact, you need to leave out optional dependencies -- class loaders that > enforce the "required" attribute of the manifest (like the webapp class > loader in Tomcat 4) would choke if Log4J, for example, was not there. > > We should still have a manifest documenting the logging package itself -- > so that *other* JARs can declare a dependency on commons-logging if > desired. would it be a good idea to add this information to the commons site? - robert -- To unsubscribe, e-mail: For additional commands, e-mail: