Return-Path: Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: (qmail 21624 invoked from network); 8 Nov 2007 21:00:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Nov 2007 21:00:40 -0000 Received: (qmail 95273 invoked by uid 500); 8 Nov 2007 21:00:28 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 95237 invoked by uid 500); 8 Nov 2007 21:00:27 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 95226 invoked by uid 99); 8 Nov 2007 21:00:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2007 13:00:27 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of will.sargent@gmail.com designates 209.85.146.183 as permitted sender) Received: from [209.85.146.183] (HELO wa-out-1112.google.com) (209.85.146.183) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2007 21:00:31 +0000 Received: by wa-out-1112.google.com with SMTP id v27so384117wah for ; Thu, 08 Nov 2007 13:00:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Yp7HjCepgThylxmgWkMrGJw8dmzWlvk4r0MejQoIeFM=; b=PeImoRmxAcxOv92RpkFEY8Ux/2z5BN1D1wnLHcg2jIQGQYZ0PAGJJb/cMsMMTrR46DfMjvMHIseTQqEjGIsEE879oLqAXSZ4vD/gBCc+l2CnT2UWeedm5s//f5NyWtgm7E204h0TtBV0kac4vZo4kcSqULoOnXEJP6y6RO0JJAQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XLv1CcpdedvhU54uE4ef/Ofk+14SE8PBQYZYJzZ2RbPFE4df1RvC175WwrIG+lsPiX1JqgOfqbIUKBtAYiRnTqXNX9bVtKE28Dj6tpSgVohVnYZcGlnbMm6ZWpn8x5AS+BZl3zHVcDXMjZ/0n5L+LPS5iWP6FWsPM8SinOA4c/U= Received: by 10.114.95.1 with SMTP id s1mr334754wab.1194555611572; Thu, 08 Nov 2007 13:00:11 -0800 (PST) Received: by 10.114.177.15 with HTTP; Thu, 8 Nov 2007 13:00:11 -0800 (PST) Message-ID: Date: Thu, 8 Nov 2007 13:00:11 -0800 From: "Will Sargent" To: "Log4J Developers List" Subject: Re: Steps for making a code contribution? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <472F832A.506@gmail.com> <47328EEB.6090807@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org > The log4j built predates that and uses a different directory > structure. I think it is very unlikely that it would go directly > into log4j itself. Probably the most reasonable course of action is > to check out the extras companion and work the classes into that > build environment. It would be fairly simple to remove all the rest > of the stuff from extras to make just a layered configurator > companion if that was the course of action. Okay, I'll make a layered configurator companion... --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org